Re: Block-level CRC checks - Mailing list pgsql-hackers

From Decibel!
Subject Re: Block-level CRC checks
Date
Msg-id 67119930-E6E0-4626-A11F-84663EE11780@decibel.org
Whole thread Raw
In response to Re: Block-level CRC checks  (Sam Mason <sam@samason.me.uk>)
List pgsql-hackers
On Oct 1, 2008, at 2:03 PM, Sam Mason wrote:
> I know you said detecting memory errors wasn't being attempted, but
> bad memory accounts for a reasonable number of reports of database
> corruption on -general so I was wondering if moving the checks around
> could catch some of these.

Down the road, I would also like to have a sanity check for data  
modification that occur while the data is in a buffer, to guard  
against memory or CPU errors. But the huge issue there is how to do  
it without killing performance. Because there's no obvious solution  
to that, I don't want to try and get it in for 8.4.
-- 
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [PATCHES] Infrastructure changes for recovery
Next
From: Gregory Stark
Date:
Subject: Re: Block-level CRC checks