Thread: transaction status error
Hi, I’m running 7.4.5 on a secondary remote database (running 8.2.5 everywhere else)
This morning I was vacuuming template1 and the other databases on this machine.
The postgres logs indicated that it removed a substantial number of commit logs,
Presumably because they were obsolete: The message was:
LOG: removing file "/var/lib/pgsql/data/pg_clog/07E7"
Jun 3 09:37:59 supra postgres[19928]: [242-1] LOG: removing file "/var/lib/pgsql/data/pg_clog/0802"
Jun 3 09:37:59 supra postgres[19928]: [243-1] LOG: removing file "/var/lib/pgsql/data/pg_clog/07E1"
Jun 3 09:37:59 supra postgres[19928]: [244-1] LOG: removing file "/var/lib/pgsql/data/pg_clog/07B7"
It removed some 100 of these logs.
A little later when I attempted to vacuum template0 I get the following error:
ERROR: could not access status of transaction 2065424697
] DETAIL: could not open file "/var/lib/pgsql/data/pg_clog/07B1": No such file or directory
Pointing to a commit log that had indeed been removed.
The end result: As far as I can tell, I have access to all the databases, including template1, which I can copy from successfully in creating
New databases. But The template0 database seems to be hosed. I can do a CREATE DATABASE from template0 but the new database
Gets the same access status error.
We are ok unless we access template0. And yes, we plan to upgrade to 8.x sometime next month. In the meantime, any ideas on how
To fix this?
Thank you,
Mark Steben
Senior Database Administrator
@utoRevenue™
A Dominion Enterprises Company
480 Pleasant Street
Suite B200
Lee, MA 01238
413-243-4800 Home Office
413-243-4809 Corporate Fax
msteben@autorevenue.com
Visit our new website at
www.autorevenue.com
IMPORTANT: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not the intended recipient (or the individual responsible for the delivery of this e-mail message to the intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received this e-mail message in error and then delete it. Thank you.
"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