Re: [HACKERS] Checksums by default? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Checksums by default?
Date
Msg-id 17720.1485223667@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Checksums by default?  (Peter Geoghegan <pg@heroku.com>)
Responses Re: [HACKERS] Checksums by default?  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Peter Geoghegan <pg@heroku.com> writes:
> I thought that checksums went in in part because we thought that there
> was some chance that they'd find bugs in Postgres.

Not really.  AFAICS the only point is to catch storage-system malfeasance.

It's barely possible that checksumming would help detect cases where
we'd written data meant for block A into block B, but I don't rate
that as being significantly more probable than bugs in the checksum
code itself.  Also, if that case did happen, the checksum code might
"detect" it in some sense, but it would be remarkably unhelpful at
identifying the actual cause.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] Checksums by default?
Next
From: Robert Haas
Date:
Subject: [HACKERS] COPY IN/BOTH vs. extended query mode