"ERROR: could not access status of transaction" (after upgrding from 9.3.2 to 9.3.4?)

From: "Cassiano, Marco" <mcassiano(at)manord(dot)com>
To: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: "ERROR: could not access status of transaction" (after upgrding from 9.3.2 to 9.3.4?)
Date: 2014-07-21 09:27:00
Message-ID: 1361CEF686657C41A139AD8C3145632B2A00F636@E2010-MB1.manord.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi all,

every weekend we use to run a batch that makes reindex/cluster of our main db.

This weekend we observed this error in the log :

2014-07-19 23:00:41 GMT 172.30.2.200(53959) dba mdn 1265998975 53caf874.6826 - ERROR: could not access status of transaction 1067517164
2014-07-19 23:00:41 GMT 172.30.2.200(53959) dba mdn 1265998975 53caf874.6826 - DETAIL: Could not open file "pg_clog/03FA": No such file or directory.
2014-07-19 23:00:41 GMT 172.30.2.200(53959) dba mdn 1265998975 53caf874.6826 - STATEMENT: cluster pk__cat_taglio on "anamat"."cat_taglio"

The previous weekend the job worked fine.

The only thing that happened in the middle (AFAIK) is that on the 17th we apply the minor upgrade of postgresql from 9.3.2 to 9.3.4.

Can you please help me to understand the cause of this corruption, how much is serious and the its correct resolution ?

By the way the data in the table seems ok : i can dump the table, I can select the data inside it.

SInce this table doesn't change frequently, we are considering a dump/delete/restore. Will this fix the problem in yuor opinion ?

Thanks a lot

Marco Cassiano

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message jayknowsunix 2014-07-21 12:51:15 Re: "ERROR: could not access status of transaction" (after upgrding from 9.3.2 to 9.3.4?)
Previous Message Tom Lane 2014-07-20 15:28:26 Re: serious issue with age(relfrozenxid)::int.