From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Steben <msteben@autorevenue.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: transaction status error
Date: Wed, 04 Jun 2008 00:02:46 -0400
Message-ID: <16374.1212552166@sss.pgh.pa.us> (raw)
In-Reply-To: <002401c8c5b1$4b188300$14010a0a@dei26g028575>
References: <002401c8c5b1$4b188300$14010a0a@dei26g028575>
"Mark Steben" <msteben@autorevenue.com> writes:
> Hi, I'm running 7.4.5 on a secondary remote database
That release is nearly four years old...
> A little later when I attempted to vacuum template0 I get the following
> error:
> ERROR: could not access status of transaction 2065424697
The 7.4.6 release notes mention something about
Repair possible failure to update hint bits on disk
Under rare circumstances this oversight could lead to "could not
access transaction status" failures, which qualifies it as a
potential-data-loss bug.
That was sufficiently long ago that I don't recall how rare the "rare
circumstances" might be. But you aren't going to rouse any interest
in investigating bugs in such an ancient release. If you care about
your data, you are supposed to keep up on minor releases.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, msteben@autorevenue.com
Subject: Re: transaction status error
In-Reply-To: <16374.1212552166@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