Re: reporting TID/table with corruption error
От | Mark Dilger |
---|---|
Тема | Re: reporting TID/table with corruption error |
Дата | |
Msg-id | AADA126D-5757-4D2F-B988-725CE50806E8@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: reporting TID/table with corruption error (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: reporting TID/table with corruption error
|
Список | 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 по дате отправления: