Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 0D7089F9F49 for ; Fri, 2 Feb 2007 23:28:49 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 30723-07 for ; Fri, 2 Feb 2007 23:28:34 -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 AE7159F9F18 for ; Fri, 2 Feb 2007 23:28:45 -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 l133SgaI026857; Fri, 2 Feb 2007 22:28:43 -0500 (EST) To: "Robert Leftwich" cc: "Peter Eisentraut" , pgsql-admin@postgresql.org Subject: Re: pg_dumpall failure - could not access status of transaction In-reply-to: <1170472173.30402.1172683791@webmail.messagingengine.com> References: <1170455123.6719.1172656201@webmail.messagingengine.com> <200702030225.19976.peter_e@gmx.net> <26353.1170469307@sss.pgh.pa.us> <1170472173.30402.1172683791@webmail.messagingengine.com> Comments: In-reply-to "Robert Leftwich" message dated "Sat, 03 Feb 2007 14:09:33 +1100" Date: Fri, 02 Feb 2007 22:28:42 -0500 Message-ID: <26856.1170473322@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/39 X-Sequence-Number: 24504 "Robert Leftwich" writes: > On Fri, 02 Feb 2007 21:21:47 -0500, "Tom Lane" said: >> 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. > [ dump snipped ] Yeah, the last part of that page has been trashed --- mostly zeroes, but there's a bit with an odd data pattern that doesn't make much sense to me: > 1a3c: d09b3000 b89b3000 a09b3000 889b3000 ..0...0...0...0. > 1a4c: 709b3000 589b3000 409b3000 289b3000 p.0.X.0.@.0.(.0. > 1a5c: 109b3000 f89a3000 e09a3000 c89a3000 ..0...0...0...0. > 1a6c: b09a3000 989a3000 809a3000 689a3000 ..0...0...0.h.0. This seems like it could indicate either a hardware or operating-system flake-out. Have you tried running hardware diagnostic tests on the machine? regards, tom lane