Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id EB3B51337B93 for ; Wed, 4 May 2011 17:27:54 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 40734-10 for ; Wed, 4 May 2011 20:27:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.virtall.com (mail.virtall.com [178.63.195.102]) by mail.postgresql.org (Postfix) with ESMTP id 355601337B61 for ; Wed, 4 May 2011 17:27:47 -0300 (ADT) Received: from mail.virtall.com (localhost [127.0.0.1]) by mail.virtall.com (Postfix) with ESMTP id 22FB0362528; Wed, 4 May 2011 22:27:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=wpkg.org; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=default; bh=BwSFQzOGz nFyrt7lzH4I9YcQ8s4=; b=cmgN2HMc8rknsflrL2YXvlh5MgeYSA1XaH6jpYfbh 2QB/U6gwT+Lu1CcpADP/HmpinZOMM/E88S+vmi0k9A9xqSAcvEPb1tFNqF2cQWfJ KDGYIySjXXqgozf7YhlaTt+z1wdEwVbC3ca/eq3qVoHMEy1iaZLUdYxh4pXpRqtq 7s= 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=jA6 M8zCNvq3fXtswwDqOpA1zIpThxnye42bwm/mxWUexA6nJ49hDps36gdNFHjZqUjD C0bdComaw0zSNQQu6BgiE3tJ39KK5pCu+FgDgHc7HNhuvpNjfSyeyy6+30sc/dV7 O2NcFY6VuW8p+hr2B/LBNrWDTPWzPsIh+mNYbWRc= Received: from [192.168.10.145] (e183095092.adsl.alicedsl.de [85.183.95.92]) by mail.virtall.com (Postfix) with ESMTPSA id 9ECCD362512; Wed, 4 May 2011 22:27:45 +0200 (CEST) Message-ID: <4DC1B6C0.2000507@wpkg.org> Date: Wed, 04 May 2011 22:27:44 +0200 From: Tomasz Chmielewski User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110419 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Scott Marlowe CC: Kevin Grittner , 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> <4DC1B378.6050105@wpkg.org> In-Reply-To: <4DC1B378.6050105@wpkg.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201105/53 X-Sequence-Number: 37490 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