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

From Andrey Borodin
Subject Re: reporting TID/table with corruption error
Date
Msg-id 924415DA-A514-4B67-AC66-E3D6C5F13F89@yandex-team.ru
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  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers

> 19 авг. 2021 г., в 21:44, Peter Geoghegan <pg@bowt.ie> написал(а):
>
> I think that this is a very good idea. Ideally this stuff would be
> more standardized.

+1
It would be great to see relation, block, offset, xmin\xmax and, probably, flags whenever
ERRCODE_DATA_CORRUPTED\ERRCODE_INDEX_CORRUPTEDis used. Iif it's possible to extract this information, of cause. This is
neededespecially in amcheck functions. 

Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Middleware Messages for FE/BE
Next
From: Andrey Borodin
Date:
Subject: Re: reporting TID/table with corruption error