From: Tom Lane <tgl@sss.pgh.pa.us>
To: kaolin fire <cognosco@tentacle.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: FATAL 2: (pg_clog ... no such file or directory)
Date: Fri, 06 Feb 2004 16:01:25 -0500
Message-ID: <12368.1076101285@sss.pgh.pa.us> (raw)
In-Reply-To: <4536F22E-58CB-11D8-ABC6-000A957FF036@tentacle.net>
References: <20030904125947.A3F73D1B89A@svr1.postgresql.org>
<4536F22E-58CB-11D8-ABC6-000A957FF036@tentacle.net>
kaolin fire <cognosco@tentacle.net> writes:
> Where would I go to start tracking down recurring error messages of the
> sort:
> FATAL 2: open of /usr/local/pgsql/data/pg_clog/06F7 failed: No such
> file or directory
> FATAL 2: open of /usr/local/pgsql/data/pg_clog/0707 failed: No such
> file or directory
> 06F7 and 0707 do not exist. Currently just looks like it goes from
> 0000 (May 14 2002) to 004F (Feb 6 2004, and counting).
Given those facts, you have corrupt data --- specifically, a wildly
out-of-range transaction number in some tuple header, causing the tuple
validity checker to try to fetch a nonexistent page of the CLOG. The
odds are good that the corruption extends further than just the one
field; that just happens to be the one that gets checked first.
There are discussions in the mailing list archives about how to locate
and clean up corrupted data. It's a pretty messy process but you can
usually get back everything except the rows on the particular corrupted
page (I'm optimistically assuming there's only one). Looking for
threads mentioning pg_filedump might be the quickest way to find info.
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, cognosco@tentacle.net
Subject: Re: FATAL 2: (pg_clog ... no such file or directory)
In-Reply-To: <12368.1076101285@sss.pgh.pa.us>
References: <20030904125947.A3F73D1B89A@svr1.postgresql.org> <4536F22E-58CB-11D8-ABC6-000A957FF036@tentacle.net> <12368.1076101285@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