Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id BBE129FA0C0 for ; Fri, 2 Feb 2007 23:49:58 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 81914-08 for ; Fri, 2 Feb 2007 23:49:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by postgresql.org (Postfix) with ESMTP id 6D98C9F9F18 for ; Fri, 2 Feb 2007 23:49:56 -0400 (AST) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id DB0ECBB8CB; Fri, 2 Feb 2007 22:49:54 -0500 (EST) Received: from web1.messagingengine.com ([10.202.2.210]) by out1.internal (MEProxy); Fri, 02 Feb 2007 22:49:54 -0500 Received: by web1.messagingengine.com (Postfix, from userid 99) id C5087255D5; Fri, 2 Feb 2007 22:49:54 -0500 (EST) Message-Id: <1170474594.565.1172687911@webmail.messagingengine.com> X-Sasl-Enc: JquQsc6sd3jgo3u+dgXJF/ob4Xoa1aAjeL4UKTW4vJUI 1170474594 From: "Robert Leftwich" To: "Tom Lane" Cc: pgsql-admin@postgresql.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface 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> <26856.1170473322@sss.pgh.pa.us> Subject: Re: pg_dumpall failure - could not access status of transaction In-Reply-To: <26856.1170473322@sss.pgh.pa.us> Date: Sat, 03 Feb 2007 14:49:54 +1100 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/40 X-Sequence-Number: 24505 On Fri, 02 Feb 2007 22:28:42 -0500, "Tom Lane" said: > This seems like it could indicate either a hardware or operating-system > flake-out. Have you tried running hardware diagnostic tests on the > machine? > A couple of weeks back when it had 'invalid page header' problems, memtest was run on it for 12-15hrs w/o a problem and smartmon didn't report any errors from the drives - I'll check smartmon again. Any other tests you would recommend? Robert