Re: [GENERAL] Undetected corruption of table files - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [GENERAL] Undetected corruption of table files
Date
Msg-id 291.1188587489@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Undetected corruption of table files  (Decibel! <decibel@decibel.org>)
Responses Re: [GENERAL] Undetected corruption of table files  (Decibel! <decibel@decibel.org>)
List pgsql-hackers
Decibel! <decibel@decibel.org> writes:
> Even if we don't care about folks running on suspect hardware, having a
> CRC would make it far more reasonable to recommend full_page_writes=3Doff.

This argument seems ridiculous.  Finding out that you have corrupt data
is no substitute for not having corrupt data.

> BTW, a method that would buy additional protection would be to compute
> the CRC for a page every time you modify it in such a way that generates
> a WAL record, and record that CRC with the WAL record. That would
> protect from corruption that happened anytime after the page was
> modified, instead of just when smgr went to write it out. How useful
> that is I don't know...

Two words: hint bits.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: enum types and binary queries
Next
From: Decibel!
Date:
Subject: Re: Password requirement in windows installer