From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Eade <seade@backstagetech.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Searching for a supposedly resolved bug report
Date: Wed, 21 Sep 2005 10:50:40 -0400
Message-ID: <14489.1127314240@sss.pgh.pa.us> (raw)
In-Reply-To: <433101E6.9080900@backstagetech.com.au>
References: <433101E6.9080900@backstagetech.com.au>
Scott Eade <seade@backstagetech.com.au> writes:
> Environment: PostgreSQL 7.3.10-RH, RHEL3
> PANIC: open of /var/lib/pgsql/data/pg_clog/0058 failed: No such file
> or directory
> I am wondering if anyone can point me to the supposedly fixed bug that
> would have caused this (is it just me or is it difficult to find
> specific bugs using the mailing list - is there an issue tracker
> somewhere?) It would be nice to know how to avoid this in the future.
I suppose Neil is thinking of this:
http://archives.postgresql.org/pgsql-hackers/2004-10/msg00464.php
which is in fact fixed as of 7.3.8 --- but if you'd updated a pre-7.3.8
installation to 7.3.10 then damage from a previous triggering of the bug
could possibly still be lurking.
Or you could have been bit by something else that happens to have a
similar-looking symptom. There's not enough info here to say.
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 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: tgl@sss.pgh.pa.us, seade@backstagetech.com.au
Subject: Re: Searching for a supposedly resolved bug report
In-Reply-To: <14489.1127314240@sss.pgh.pa.us>
References: <433101E6.9080900@backstagetech.com.au> <14489.1127314240@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