| 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-06 22:23:40 |
| Message-ID: | CAH2-Wzm1he651X9NKiBtuBa5D7i7dw0zfY9X699+3OKpnW4=ug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Mar 6, 2020 at 1:38 AM Victor Yegorov <vyegorov(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2020-03-08 00:45:27 | Re: BUG #16285: bt_metap fails with value is out of range for type integer |
| Previous Message | Radics, Geza | 2020-03-06 19:33:23 | Re: JSON array is not updated if updating with empty array |