From: Robert Leftwich <pg@rtl.fmailbox.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dumpall failure - could not access status of transaction
Date: Sat, 03 Feb 2007 14:49:54 +1100
Message-ID: <1170474594.565.1172687911@webmail.messagingengine.com> (raw)
In-Reply-To: <26856.1170473322@sss.pgh.pa.us>
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>
On Fri, 02 Feb 2007 22:28:42 -0500, "Tom Lane" <tgl@sss.pgh.pa.us> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: pg@rtl.fmailbox.com, tgl@sss.pgh.pa.us
Subject: Re: pg_dumpall failure - could not access status of transaction
In-Reply-To: <1170474594.565.1172687911@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> <26856.1170473322@sss.pgh.pa.us> <1170474594.565.1172687911@webmail.messagingengine.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox