| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-10-02 22:35:25 | Re: Block-level CRC checks |
| Previous Message | Simon Riggs | 2008-10-02 22:11:28 | Re: [PATCHES] Infrastructure changes for recovery |