Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [GENERAL] Undetected corruption of table files
- From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
- To: Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at>
- Cc: Tom Lane *EXTERN* <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: [GENERAL] Undetected corruption of table files
- Date: Fri, 31 Aug 2007 08:08:43 -0400
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.
Jan -- #======================================================================# # 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 #
- Follow-Ups:
- Re: [GENERAL] Undetected corruption of table files
- From: Albe Laurenz
- Re: [GENERAL] Undetected corruption of table files
- References:
- Re: [GENERAL] Undetected corruption of table files
- From: Albe Laurenz
- Re: [GENERAL] Undetected corruption of table files
- From: Tom Lane
- Re: [GENERAL] Undetected corruption of table files
- From: Albe Laurenz
- Re: [GENERAL] Undetected corruption of table files
- Prev by Date: Re: Performing antijoin in postgres
- Next by Date: Re: [GENERAL] Undetected corruption of table files
- Previous by thread: Re: [GENERAL] Undetected corruption of table files
- Next by thread: Re: [GENERAL] Undetected corruption of table files
- Indexes: