Re: Checksum errors in pg_stat_database - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Checksum errors in pg_stat_database
Date
Msg-id CABUevExj9RaZdqnu2q+oMBcB_mZAd2iBzEuZw4+-VQmJw4byRg@mail.gmail.com
Whole thread Raw
In response to Re: Checksum errors in pg_stat_database  (David Steele <david@pgmasters.net>)
Responses Re: Checksum errors in pg_stat_database  (Julien Rouhaud <rjuju123@gmail.com>)
Re: Checksum errors in pg_stat_database  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
On Sat, Jan 12, 2019 at 5:16 AM David Steele <david@pgmasters.net> wrote:
On 1/11/19 10:25 PM, Magnus Hagander wrote:
> On Fri, Jan 11, 2019 at 9:20 PM Tomas Vondra
>     On 1/11/19 7:40 PM, Robert Haas wrote:
>      > But I'm tentatively in favor of your proposal anyway, because it's
>      > pretty simple and cheap and might help people, and doing something
>      > noticeably better is probably annoyingly complicated.
>      >
>
>     +1
>
> Yeah, that's the idea behind it -- it's cheap, and an
> early-warning-indicator.

+1

PFA is a patch to do this.

It tracks things that happen in the general backends. Possibly we should also consider counting the errors actually found when running base backups? OTOH, that part of the code doesn't really track things like databases (as it operates just on the raw data directory underneath), so that implementation would definitely not be as clean...

--
Attachment

pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: Problems with plan estimates in postgres_fdw
Next
From: Magnus Hagander
Date:
Subject: Re: Remove Deprecated Exclusive Backup Mode