DomainKey-Signature: a=rsa-sha1; c=nofws; d=wpkg.org; h=message-id:date
	:from:mime-version:to:cc:subject:references:in-reply-to
	:content-type:content-transfer-encoding; q=dns; s=default; b=tUw
	baPHmooh/ETQ9h8xLNtwn+8FPiXn5qxYYj7wO2sTO8Vrv59nJfXjSBfuLt0+MSgm
	9pTOTJChDxpYuhnHadk7e1v88mJ1gTwep55K8esFJlAshZhQjm4h/MDBViZ+Fdt+
	Hm/pXbrChVv5941TN9vg34jTeKQpsMzpobtjwpKc=
Message-ID: <4DC3B469.80004@wpkg.org>
Date: Fri, 06 May 2011 10:42:17 +0200
From: Tomasz Chmielewski <tch@wpkg.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Scott Marlowe <scott.marlowe@gmail.com>
CC: Kevin Grittner <Kevin.Grittner@wicourts.gov>, pgsql-admin@postgresql.org
Subject: Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such
	file or directory' - what to do now?
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>
In-Reply-To: <4DC1B6C0.2000507@wpkg.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 04.05.2011 22:27, Tomasz Chmielewski 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?

Nobody has a clue? :|


-- 
Tomasz Chmielewski
http://wpkg.org