Re: reporting TID/table with corruption error - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: reporting TID/table with corruption error
Date
Msg-id AADA126D-5757-4D2F-B988-725CE50806E8@enterprisedb.com
Whole thread Raw
In response to Re: reporting TID/table with corruption error  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: reporting TID/table with corruption error  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers

> On Aug 19, 2021, at 10:57 AM, Peter Geoghegan <pg@bowt.ie> wrote:
>
> High
> verbosity makes a lot of sense here.

Works for me.  We could create another function, "verify_heapam_full" perhaps, that returns additional columns matching
thosefrom pageinspect's heap_page_items(): 

    OUT lp smallint,
    OUT lp_off smallint,
    OUT lp_flags smallint,
    OUT lp_len smallint,
    OUT t_xmin xid,
    OUT t_xmax xid,
    OUT t_field3 int4,
    OUT t_ctid tid,
    OUT t_infomask2 integer,
    OUT t_infomask integer,
    OUT t_hoff smallint,
    OUT t_bits text,
    OUT t_oid oid,
    OUT t_data bytea

Should it also return the full page?  That would be quite verbose (an extra 8k per row), but it could be fed into any
ofpageinspect's functions for further analysis. 

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company






pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: badly calculated width of emoji in psql
Next
From: Bruce Momjian
Date:
Subject: Re: strange case of "if ((a & b))"