From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-admin@postgresql.org
Cc: Robert Leftwich <pg@rtl.fmailbox.com>
Subject: Re: pg_dumpall failure - could not access status of transaction
Date: Sat, 3 Feb 2007 02:25:18 +0100
Message-ID: <200702030225.19976.peter_e@gmx.net> (raw)
In-Reply-To: <1170455123.6719.1172656201@webmail.messagingengine.com>
References: <1170455123.6719.1172656201@webmail.messagingengine.com>
Robert Leftwich wrote:
> pg_dump: Error message from server: ERROR: could not access status
> of transaction 3183024
> DETAIL: could not open file "pg_clog/0003": No such file or
> directory
If your database system has already experienced on the order of 3183024
transactions, then you should wonder where that file went. Otherwise
you probably have garbage on disk, pointing to a transaction that
hasn't happened yet. This is usually hardware trouble in any case,
unless you have actually deleted the file manually.
The alternative is that your database system has already seen more than
2^32 transactions and you have hit some bug in the transaction
wraparound, but that would be much less likely than the above cases.
> I'm (obviously) lost here - what is the correct way to track down the
> appropriate file and record to point pg_filedump at to view any
> corruption?
Look for something that contains 3183024 as a four-byte integer.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
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: peter_e@gmx.net, pg@rtl.fmailbox.com
Subject: Re: pg_dumpall failure - could not access status of transaction
In-Reply-To: <200702030225.19976.peter_e@gmx.net>
References: <1170455123.6719.1172656201@webmail.messagingengine.com> <200702030225.19976.peter_e@gmx.net>
* 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