From: | Tomasz Chmielewski <mangoo(at)wpkg(dot)org> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-admin(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-30 09:18:17 |
Message-ID: | 4DE360D9.5060300@wpkg.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
On 07.05.2011 23:19, Tomasz Chmielewski wrote:
> On 06.05.2011 10:42, Tomasz Chmielewski wrote:
>>> bookstor=# SELECT 1 FROM core_wot_seq FOR UPDATE;
>>> ERROR: could not access status of transaction 1573786613
>>> DETAIL: Could not open file "pg_clog/05DC": No such file or directory.
>>>
>>> How do I best recover from this? Stop postgres, create an empty, 256k
>>> pg_clog/05DC file, start postgres?
>>>
>>> Export table, drop table, import table? Anything else?
>>
>> Nobody has a clue? :|
>
> Just as a follow up, it turned out several sequences, and only sequences
> were affected this way.
>
> I used pg_dump to export these sequences, dropped the sequences, and
> imported them again.
Unfortunately, the issue is back, and again, only affects sequences.
I'd be really grateful for any more ideas here (why it happens, how to
best recover from it)!
--
Tomasz Chmielewski
http://wpkg.org
From | Date | Subject | |
---|---|---|---|
Next Message | Cédric Villemain | 2011-05-30 10:25:29 | Re: Insert statement deletes older table records |
Previous Message | Scott Marlowe | 2011-05-30 04:21:34 | Re: Insert statement deletes older table records |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2011-05-30 09:36:04 | Re: SSI predicate locking on heap -- tuple or row? |
Previous Message | Leonardo Francalanci | 2011-05-30 07:51:14 | Re: switch UNLOGGED to LOGGED |