| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Victor Yegorov <vyegorov(at)gmail(dot)com>, 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-09 22:09:30 |
| Message-ID: | 20200309220930.ozdulsvymhfgm4dq@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2020-03-07 16:45:27 -0800, Peter Geoghegan wrote:
> 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!
ISTM that we need some fix for the back-branches too. Being unable to
look at some indexes till 12 has aged out doesn't strike me as good.
How about simply printing the wrapped value? That's far from perfect, of
course, but clearly better than the current situation in the back
branches.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jack Tseng | 2020-03-09 22:25:03 | Re: select big table postgresql crash |
| Previous Message | Logan Bowers | 2020-03-09 21:05:27 | Optimizer Doesn't Push Down Where Expressions on Rollups |