From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Einar Indridason <einari(at)f-prot(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: FAQ (disk space) |
Date: | 2004-01-26 14:25:29 |
Message-ID: | 7198.1075127129@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> On Mon, Jan 26, 2004 at 10:48:55AM +0000, Einar Indridason wrote:
>> Would it be worth it to calculate some sort of a checksum over a row, and
>> store that checksum along with the row?
> There has been discussion about checksumming entire pages and AFAIK they are
> in the WAL, I just don't think they in the main data store.
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. In practice there
are other ways to detect errors (eg, cross-checking of page header
fields) that seem to get the job done for us. Also, even when you do
have a corrupted page, having the system refuse to touch it at all is
not necessarily the behavior you want --- you're going to want to see
what data you can extract.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Wilson | 2004-01-26 14:43:38 | Re: Casting varchar to interval.? |
Previous Message | D. Dante Lorenso | 2004-01-26 12:57:30 | Casting varchar to interval.? |