Skip site navigation (1) Skip section navigation (2)

Re: Block-level CRC checks

From: Decibel! <decibel(at)decibel(dot)org>
To: Sam Mason <sam(at)samason(dot)me(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Block-level CRC checks
Date: 2008-10-02 22:23:41
Message-ID: 67119930-E6E0-4626-A11F-84663EE11780@decibel.org (view raw or flat)
Thread:
Lists: 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(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828


In response to

pgsql-hackers by date

Next:From: Gregory StarkDate: 2008-10-02 22:35:25
Subject: Re: Block-level CRC checks
Previous:From: Simon RiggsDate: 2008-10-02 22:11:28
Subject: Re: [PATCHES] Infrastructure changes for recovery

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group