Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 251BC9FB27D for ; Fri, 2 Feb 2007 22:21:57 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 30961-06 for ; Fri, 2 Feb 2007 22:21:43 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 498939FA2F4 for ; Fri, 2 Feb 2007 22:21:54 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l132LlXC026354; Fri, 2 Feb 2007 21:21:47 -0500 (EST) To: Peter Eisentraut cc: pgsql-admin@postgresql.org, "Robert Leftwich" 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> Comments: In-reply-to Peter Eisentraut message dated "Sat, 03 Feb 2007 02:25:18 +0100" Date: Fri, 02 Feb 2007 21:21:47 -0500 Message-ID: <26353.1170469307@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/37 X-Sequence-Number: 24502 Peter Eisentraut 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