Horton

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

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: vyegorov@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2020-03-03T01:39:36Z
Lists: pgsql-bugs 
On 2020-Mar-02, PG Bug reporting form wrote:

> I have an index, that is giving issues pageinspect-ing it:
> 
> SELECT * FROM bt_metap('index')\gx
> ERROR:  value "2180413846" is out of range for type integer

I understand it's gone now, but you could have used \errverbose to
display the source function name that caused the error, followed by
setting backtrace_functions to that function and repeated the query.
That may have resulted in a more precise location of the problem.

Thanks,

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Paper over bt_metap() oldest_xact bug in backbranches.

  2. pageinspect: Fix types used for bt_metap() columns.

  3. Skip full index scan during cleanup of B-tree indexes when possible

  4. pg_stat_statements: Widen query IDs from 32 bits to 64 bits.