From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-admin@postgresql.org, "Robert Leftwich" <pg@rtl.fmailbox.com>
Subject: Re: pg_dumpall failure - could not access status of transaction
Date: Fri, 02 Feb 2007 21:21:47 -0500
Message-ID: <26353.1170469307@sss.pgh.pa.us> (raw)
In-Reply-To: <200702030225.19976.peter_e@gmx.net>
References: <1170455123.6719.1172656201@webmail.messagingengine.com>
<200702030225.19976.peter_e@gmx.net>
Peter Eisentraut <peter_e@gmx.net> writes:
> 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.
Yeah. What file names are actually present in $PGDATA/pg_clog/, and
what does pg_controldata say about the current XID counter? We have
seen some bugs where clog files get deleted before they're not needed
anymore :-(
Also, can you show us the pg_filedump output for the page of
pg_description you think is trashed? I find "-i -f" options give
the most useful output usually.
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, peter_e@gmx.net, pg@rtl.fmailbox.com
Subject: Re: pg_dumpall failure - could not access status of transaction
In-Reply-To: <26353.1170469307@sss.pgh.pa.us>
References: <1170455123.6719.1172656201@webmail.messagingengine.com> <200702030225.19976.peter_e@gmx.net> <26353.1170469307@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