From: Tom Lane <tgl@sss.pgh.pa.us>
To: Edoardo Ceccarelli <eddy@axa.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_clog
Date: Mon, 18 Dec 2006 14:55:49 -0500
Message-ID: <27860.1166471749@sss.pgh.pa.us> (raw)
In-Reply-To: <2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.com>
References: <2c5b22d10612180957s78fa6fd8s9f913673bfadbe0e@mail.gmail.com>
<25199.1166467713@sss.pgh.pa.us>
<2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.com>
"Edoardo Ceccarelli" <eddy@axa.it> writes:
> I bet a crashing process could cause that data corruption, right?
No, Postgres is remarkably resistant to causing corruption during a
crash; it's deliberately engineered that way. I don't say this
*couldn't* be the explanation but it shouldn't be your first guess.
Frankly I think hardware flakiness is more likely.
There are currently two known crashing bugs in 8.2.0, and both of them
will result in a simple crash, no data corruption.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, eddy@axa.it
Subject: Re: pg_clog
In-Reply-To: <27860.1166471749@sss.pgh.pa.us>
References: <2c5b22d10612180957s78fa6fd8s9f913673bfadbe0e@mail.gmail.com> <25199.1166467713@sss.pgh.pa.us> <2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.com> <27860.1166471749@sss.pgh.pa.us>
* 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