| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tomasz Chmielewski <mangoo(at)wpkg(dot)org> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now? |
| Date: | 2011-05-31 03:16:53 |
| Message-ID: | 16063.1306811813@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Tomasz Chmielewski <mangoo(at)wpkg(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomasz Chmielewski | 2011-05-31 08:26:58 | Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now? |
| Previous Message | Cédric Villemain | 2011-05-30 10:25:29 | Re: Insert statement deletes older table records |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-05-31 03:42:27 | Re: Getting a bug tracker for the Postgres project |
| Previous Message | Greg Stark | 2011-05-31 03:08:28 | Re: Getting a bug tracker for the Postgres project |