Skip site navigation (1) Skip section navigation (2)

Re: Unable to explain DB error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Steven Rosenstein <srosenst(at)us(dot)ibm(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Unable to explain DB error
Date: 2005-07-28 18:19:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Steven Rosenstein <srosenst(at)us(dot)ibm(dot)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

			regards, tom lane

In response to

pgsql-performance by date

Next:From: Luke LonerganDate: 2005-07-28 18:27:36
Subject: Re: Finding bottleneck
Previous:From: Tom LaneDate: 2005-07-28 18:13:51
Subject: Re: Left joining against two empty tables makes a query

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group