Re: Logging corruption error codes - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: Logging corruption error codes
Date
Msg-id 3695257b-f39e-be01-17bd-77ae8dd5510d@2ndquadrant.com
Whole thread Raw
In response to Logging corruption error codes  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: Logging corruption error codes  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-bugs
On 2019-06-20 11:57, Andrey Borodin wrote:
> We are fine-tuning our data corruption monitoring and found out that many corruption cases do not report proper error
code.
> This makes automatic log analyzer way too smart program.
> We think that corruption error codes should be given in cases when B-tree or TOAST do not know how to interpret
data.
> PFA patch with cases that we have found in logs and consider evidence of corruption.
> 
> Best regards, Andrey Borodin.

Should we use errmsg_internal() in the adjusted calls, so that the error
messages are not picked up for translation?  I could go either way, but
it's something that should be considered.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15921: invalid regular expression while parsing hunspell affix
Next
From: Tom Lane
Date:
Subject: Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail