Re: transaction status error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mark Steben" <msteben(at)autorevenue(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: transaction status error
Date: 2008-06-04 04:02:46
Message-ID: 16374.1212552166@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Mark Steben" <msteben(at)autorevenue(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Mikel Lindsaar 2008-06-04 06:39:59 unrecognized configuration parameter "synchronize_seqscans"
Previous Message Mark Steben 2008-06-03 19:37:43 transaction status error