From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: FAQ (disk space) |
Date: | 2004-01-26 16:13:32 |
Message-ID: | 87zncau1qr.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> This has been discussed, as Martijn says, and I believe the consensus
> was that the benefits wouldn't exceed the costs. Note that a checksum
> does not magically prevent errors, it just means that you will detect
> errors and refuse to access potentially-corrupt data.
Well there are ECC codes that allow correcting errors as well. But I don't see
how that would help. You would have to check on every single memory access
since it's likely memory that will cause single bit errors, not disk. Disk is
more likely to give entire bad blocks.
I think the moral is that if you are afraid of single bit errors corrupting
data then you should probably spec out a server with ECC ram.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-01-26 16:37:57 | Re: Casting varchar to interval.? |
Previous Message | Eric Ridge | 2004-01-26 16:05:35 | Re: Storing Configuration settings for a database? |