From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@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 11:18:17 +0200
Message-ID: <4DE360D9.5060300@wpkg.org> (raw)
In-Reply-To: <4DC5B754.3040506@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>
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
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: mangoo@wpkg.org, scott.marlowe@gmail.com, Kevin.Grittner@wicourts.gov
Subject: Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now?
In-Reply-To: <4DE360D9.5060300@wpkg.org>
* 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