Re: Logging corruption error codes

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Logging corruption error codes
Дата
Msg-id 3695257b-f39e-be01-17bd-77ae8dd5510d@2ndquadrant.com
обсуждение исходный текст
Ответ на Logging corruption error codes  (Andrey Borodin <x4mmm@yandex-team.ru>)
Ответы Re: Logging corruption error codes  (Andrey Borodin <x4mmm@yandex-team.ru>)
Список 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 по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15921: invalid regular expression while parsing hunspell affix
Следующее
От: Tom Lane
Дата:
Сообщение: Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail