Re: BUG #16285: bt_metap fails with value is out of range for type integer

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Victor Yegorov <vyegorov(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16285: bt_metap fails with value is out of range for type integer
Date: 2020-03-08 00:45:27
Message-ID: CAH2-Wz=esJqUO_QTasnjGPHvER7Bo5iac04UgUqR7V7N-YPMDg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Mar 6, 2020 at 2:23 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> This has to be the oldest_xact field. If it was any of the other
> fields, the "%d" format would not result in an error (it would just
> result in incorrectly displaying a negative integer). oldest_xact is
> the only field that uses "%u" (unfortunately, the declaration makes
> the field an int4/integer, so you may see this error).

Pushed a fix for this just now.

Thanks for the report!

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Victor Yegorov 2020-03-08 07:47:20 Re: BUG #16285: bt_metap fails with value is out of range for type integer
Previous Message Peter Geoghegan 2020-03-06 22:23:40 Re: BUG #16285: bt_metap fails with value is out of range for type integer