From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now?
Date: Mon, 30 May 2011 23:16:53 -0400
Message-ID: <16063.1306811813@sss.pgh.pa.us> (raw)
In-Reply-To: <4DE360D9.5060300@wpkg.org>
References: <4DC0F063.70306@wpkg.org>
<4DC15137020000250003D295@gw.wicourts.gov>
<4DC19CD1.7070600@wpkg.org>
<BANLkTikG3yN0xB_wTy1SVYOrA9E=FNBZLg@mail.gmail.com>
<4DC1B378.6050105@wpkg.org>
<4DC1B6C0.2000507@wpkg.org>
<4DC3B469.80004@wpkg.org>
<4DC5B754.3040506@wpkg.org>
<4DE360D9.5060300@wpkg.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, mangoo@wpkg.org, scott.marlowe@gmail.com, Kevin.Grittner@wicourts.gov, pgsql-hackers@postgresql.org
Subject: Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now?
In-Reply-To: <16063.1306811813@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox