From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steven Rosenstein <srosenst@us.ibm.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Unable to explain DB error
Date: Thu, 28 Jul 2005 14:19:28 -0400
Message-ID: <25774.1122574768@sss.pgh.pa.us> (raw)
In-Reply-To: <OFFB0048A5.CE2093BE-ON8525704C.005CB3DF-8525704C.005D646E@us.ibm.com>
References: <OFFB0048A5.CE2093BE-ON8525704C.005CB3DF-8525704C.005D646E@us.ibm.com>
Steven Rosenstein <srosenst@us.ibm.com> writes:
> Any idea why Postgres would be looking for a clog file name 0FC0 when the most recent filename is 04CE?
Corrupt data --- specifically a bad transaction number in a tuple
header. (In practice, this is the first field looked at in which
we can readily detect an error, so you tend to see this symptom for
any serious data corruption situation. The actual fault may well
be something like a corrupt page header causing the code to follow
"tuple pointers" that point to garbage.)
See the PG list archives for past discussions of dealing with corrupt
data. pgsql-performance is pretty off-topic for this.
BTW, PG 7.4 and up handle this sort of thing much more gracefully ...
they can't resurrect corrupt data of course, but they tend not to
panic.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, srosenst@us.ibm.com
Subject: Re: Unable to explain DB error
In-Reply-To: <25774.1122574768@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