Re: [ADMIN] 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [ADMIN] 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now?
Date
Msg-id 16063.1306811813@sss.pgh.pa.us
Whole thread Raw
Responses Re: [ADMIN] 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now?  (Tomasz Chmielewski <mangoo@wpkg.org>)
List pgsql-hackers
Tomasz Chmielewski <mangoo@wpkg.org> writes:
> bookstor=# SELECT 1 FROM core_wot_seq FOR UPDATE;

Um ... why are you doing that on a sequence?

> ERROR: could not access status of transaction 1573786613
> DETAIL: Could not open file "pg_clog/05DC": No such file or directory.

This doesn't surprise me too much, because sequences are not expected
to contain any live XIDs, so the XID freezing mechanism ignores them.
So if you did that in the past, this would eventually happen.

I think the most appropriate solution may be to disallow SELECT FOR
UPDATE/SHARE on sequences ... so if you have a good reason why we
shouldn't do so, please explain it.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Getting a bug tracker for the Postgres project
Next
From: Tom Lane
Date:
Subject: Re: Getting a bug tracker for the Postgres project