Re: BUG #16285: bt_metap fails with value is out of range for type integer - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #16285: bt_metap fails with value is out of range for type integer
Date
Msg-id CAH2-Wzm1he651X9NKiBtuBa5D7i7dw0zfY9X699+3OKpnW4=ug@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16285: bt_metap fails with value is out of range for type integer  (Victor Yegorov <vyegorov@gmail.com>)
Responses Re: BUG #16285: bt_metap fails with value is out of range for type integer  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-bugs
On Fri, Mar 6, 2020 at 1:38 AM Victor Yegorov <vyegorov@gmail.com> wrote:
> It is not entirely gone, I still have some indexes around that produce this.
> This backtracing functionality is available only in the HEAD as far as I can see, so it took me a while
> to get to it:
>
> [3760] ERROR:  value "4282444360" is out of range for type integer

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).


--
Peter Geoghegan



pgsql-bugs by date:

Previous
From: "Radics, Geza"
Date:
Subject: Re: JSON array is not updated if updating with empty array
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #16285: bt_metap fails with value is out of range for type integer