Re: pg_dumpall failure - could not access status of transaction - Mailing list pgsql-admin

From Tom Lane
Subject Re: pg_dumpall failure - could not access status of transaction
Date
Msg-id 26353.1170469307@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dumpall failure - could not access status of transaction  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_dumpall failure - could not access status of transaction  ("Robert Leftwich" <pg@rtl.fmailbox.com>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_dumpall failure - could not access status of transaction
Next
From: "Robert Leftwich"
Date:
Subject: Re: pg_dumpall failure - could not access status of transaction