From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jean-Denis Girard <jd-girard@esoft.pf>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Fatal error
Date: Wed, 04 Sep 2002 00:30:37 -0400
Message-ID: <24485.1031113837@sss.pgh.pa.us> (raw)
In-Reply-To: <3D75818D.9020909@esoft.pf>
References: <3D75818D.9020909@esoft.pf>
Jean-Denis Girard <jd-girard@esoft.pf> writes:
> Last tuesday I upgraded a production DB from 7.1 to 7.2.
7.2? I'd hope you went to 7.2.2, or at least 7.2.1.
> FATAL 2: open of /var/lib/pgsql/data/pg_clog/0323 failed: No such file
> or directory
This message implies a bad xmin or xmax field in a stored tuple. We've
seen a number of reports of similar failures, but so far the evidence
has pointed to hardware failures rather than a software problem ---
corrupted data on disk would usually trigger this kind of failure before
anything else, so the particular error message doesn't seem very
significant.
> Don't know what to do and any help will be welcome. I can also provide
> more specific information if needed.
You should probably first try some hardware diagnostics like "memtest86"
and "badblocks".
I don't want to sound like I'm dismissing the possibility that it's a
Postgres bug. It could be ... but without more evidence there's not
much I can do to poke into it.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, jd-girard@esoft.pf
Subject: Re: Fatal error
In-Reply-To: <24485.1031113837@sss.pgh.pa.us>
* 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