Re: reporting TID/table with corruption error

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: reporting TID/table with corruption error
Date: 2021-08-19 17:17:41
Message-ID: 924415DA-A514-4B67-AC66-E3D6C5F13F89@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 19 авг. 2021 г., в 21:44, Peter Geoghegan <pg(at)bowt(dot)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_CORRUPTED is used. Iif it's possible to extract this information, of cause. This is needed especially in amcheck functions.

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2021-08-19 17:28:40 Re: reporting TID/table with corruption error
Previous Message Simon Riggs 2021-08-19 17:13:20 Re: Middleware Messages for FE/BE