On 8/28/2007 4:14 AM, Albe Laurenz wrote:
> Not all databases are on enterprise scale storage systems, and
> there's also the small possibility of PostgreSQL bugs that could
> be detected that way.
Computing a checksum just before writing the block will NOT detect any
faulty memory or Postgres bug that corrupted the block. You will have a
perfectly fine checksum over the corrupted data.
A checksum only detects corruptions that happen between write and read.
Most data corruptions that happen during that time however lead to some
sort of read error reported by the disk.
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
In response to
pgsql-hackers by date
|Next:||From: Albe Laurenz||Date: 2007-08-31 12:34:09|
|Subject: Re: [GENERAL] Undetected corruption of table files|
|Previous:||From: Gregory Stark||Date: 2007-08-31 09:36:13|
|Subject: Re: Performing antijoin in postgres|
pgsql-general by date
|Next:||From: Sibte Abbas||Date: 2007-08-31 12:33:34|
|Subject: Fwd: Query the catalog|
|Previous:||From: Magnus Hagander||Date: 2007-08-31 11:47:07|
|Subject: Re: PostgreSQL with Kerberos and Active Directory|