| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, 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-07-22 11:16:21 |
| Message-ID: | 3695257b-f39e-be01-17bd-77ae8dd5510d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-07-22 21:41:26 | Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail |
| Previous Message | PG Bug reporting form | 2019-07-22 11:12:09 | BUG #15921: invalid regular expression while parsing hunspell affix |