From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Craig Ringer <ringerc@ringerc.id.au>
Cc: Raj Gandhi <raj01gandhi@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Detecting DB corruption
Date: Wed, 31 Oct 2012 23:10:25 -0600
Message-ID: <F4929CDE-D583-4075-8061-4285E3D813C8@elevated-dev.com> (raw)
In-Reply-To: <5091E377.2030505@ringerc.id.au>
References: <CALU_HCPC7Vq60cq7=U7KDUdNGWwBbAhNvHb05EF5iOfvAc16Mw@mail.gmail.com>
<5091E377.2030505@ringerc.id.au>
On Oct 31, 2012, at 8:50 PM, Craig Ringer wrote:
> Seriously, if you're facing DB corruption then something is already
> horribly wrong with your setup.
True, but. In a past life, complaints from the db (it was a db that stored a checksum with every block) were the very first symptom when something went horribly wrong with the hardware. (Partial short between wires of an internal SCSI cable; eventually we determined that about every 1MB, 1 bit would get flipped between the controller & disk.)
So, if there were an official db verifier tool for PG, I for one would have it run periodically.
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, ringerc@ringerc.id.au, raj01gandhi@gmail.com
Subject: Re: Detecting DB corruption
In-Reply-To: <F4929CDE-D583-4075-8061-4285E3D813C8@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox