Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now?

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-04 20:27:44
Message-ID: 4DC1B6C0.2000507@wpkg.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On 04.05.2011 22:13, Tomasz Chmielewski wrote:
> On 04.05.2011 21:50, Scott Marlowe wrote:
>
>> Then another pg_clog file disappeared.

OK, I have:

bookstor=# SELECT * FROM core_wot_seq;
sequence_name | last_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled | is_called
------------------+------------+--------------+---------------------+-----------+-------------+---------+-----------+-----------
core_wot_seq | 2593 | 1 | 9223372036854775807 | 1 | 1 | 8 | f | t
(1 row)

bookstor=# SELECT 1 FROM core_wot_seq;
?column?
----------
1
(1 row)

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?

--
Tomasz Chmielewski
http://wpkg.org

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Dinesh Bhandary 2011-05-04 21:55:58 worker took too long to start; cancelled ( postgres 9.0.3)
Previous Message Tomasz Chmielewski 2011-05-04 20:13:44 Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now?

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2011-05-04 20:33:25 Re: VARIANT / ANYTYPE datatype
Previous Message Kevin Grittner 2011-05-04 20:26:43 Re: Unlogged vs. In-Memory