Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id C7A5A9FA1BB for ; Fri, 2 Feb 2007 21:24:23 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 03785-06 for ; Fri, 2 Feb 2007 21:24:23 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by postgresql.org (Postfix) with SMTP id D57CA9FA197 for ; Fri, 2 Feb 2007 21:24:22 -0400 (AST) Received: (qmail invoked by alias); 03 Feb 2007 01:24:20 -0000 Received: from ip-90-186-2-0.web.vodafone.de (EHLO colt.pezone.net) [90.186.2.0] by mail.gmx.net (mp039) with SMTP; 03 Feb 2007 02:24:20 +0100 X-Authenticated: #495269 From: Peter Eisentraut To: pgsql-admin@postgresql.org Subject: Re: pg_dumpall failure - could not access status of transaction Date: Sat, 3 Feb 2007 02:25:18 +0100 User-Agent: KMail/1.9.5 Cc: "Robert Leftwich" References: <1170455123.6719.1172656201@webmail.messagingengine.com> In-Reply-To: <1170455123.6719.1172656201@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702030225.19976.peter_e@gmx.net> X-Y-GMX-Trusted: 0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/36 X-Sequence-Number: 24501 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/