Re: Logging corruption error codes

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Анна Крханбарова <annkpx(at)yandex-team(dot)ru>, Dmitriy Sarafannikov <dsarafan(at)yandex-team(dot)ru>
Subject: Re: Logging corruption error codes
Date: 2019-08-01 09:42:11
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

> 1 авг. 2019 г., в 14:26, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> написал(а):
> On 2019-07-31 08:07, Andrey Borodin wrote:
>> Please find attached patch v2: added a little more cases with corruption.
> Committed with some adjustments.
Many thanks!

> Note that your patch didn't compile at all. Please check that next time.

Uh...sorry. I've tried to cope with formatting and finally check-world'ed without saved tab.
I see you adjusted ERRCODE_DATA_CORRUPTED -> ERRCODE_INDEX_CORRUPTED in one place, that is also my mistake.

Thank you!

Best regards, Andrey Borodin.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Sergei Kornilov 2019-08-01 10:42:29 Re: BUG #15936: user defined data type isn't picking default value
Previous Message Peter Eisentraut 2019-08-01 09:26:32 Re: Logging corruption error codes