Re: transaction status error - Mailing list pgsql-admin

From Tom Lane
Subject Re: transaction status error
Date
Msg-id 16374.1212552166@sss.pgh.pa.us
Whole thread Raw
In response to transaction status error  ("Mark Steben" <msteben@autorevenue.com>)
List pgsql-admin
"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

pgsql-admin by date:

Previous
From: "Mark Steben"
Date:
Subject: transaction status error
Next
From: "Mikel Lindsaar"
Date:
Subject: unrecognized configuration parameter "synchronize_seqscans"