Re: Page Checksums - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Page Checksums
Date
Msg-id CA+Tgmoau8hcHgZe0jrvp0eM4+DzzLTagt692SiOdo0ehpbx2Bw@mail.gmail.com
Whole thread Raw
In response to Re: Page Checksums  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Page Checksums  (Christopher Browne <cbbrowne@gmail.com>)
Re: Page Checksums  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Mon, Dec 19, 2011 at 2:44 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> I was thinking that we would warn when such was found, set hint bits
> as needed, and rewrite with the new CRC.  In the unlikely event that
> it was a torn hint-bit-only page update, it would be a warning about
> something which is a benign side-effect of the OS or hardware crash.

But that's terrible.  Surely you don't want to tell people:

WARNING:  Your database is corrupted, or maybe not.  But don't worry,
I modified the data block so that you won't get this warning again.

OK, I guess I'm not sure that you don't want to tell people that.  But
*I* don't!

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgstat wait timeout
Next
From: Robert Haas
Date:
Subject: Re: sync_seqscans in postgresql.conf