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

From Julien Rouhaud
Subject Re: Checksum errors in pg_stat_database
Date
Msg-id CAOBaU_anyeHuG42W1PEUY922MPz+rMdEMpe8R_EtfxN9_g4ggg@mail.gmail.com
Whole thread Raw
In response to Re: Checksum errors in pg_stat_database  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Checksum errors in pg_stat_database
List pgsql-hackers
Sorry for delay, I had to catch a train.

On Sat, Mar 30, 2019 at 4:02 PM Magnus Hagander <magnus@hagander.net> wrote:
>
> My vote is still to drop it completely, but if we're keeping it, it has to go in both paths.

Ok.  For now I'm attaching v2, which drops this field, rename the view
to pg_stat_checksums (terminal s), and use the policy for choosing
random oid in the 8000..9999 range for new functions.

I'd also have to get more feedback on this.  For now, I'll add this
thread to the pg12 open items, as a follow up of the initial code
drop.

> Technically, that should be in pg_stat_progress_checksums to be consistent :) So whichever way we turn, it's going to
beinconsistent with something.
 

Indeed :)

Attachment

pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: Berserk Autovacuum (let's save next Mandrill)
Next
From: Fabien COELHO
Date:
Subject: Re: Progress reporting for pg_verify_checksums