Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 1760BB603AB for ; Mon, 30 May 2011 18:18:31 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 71746-01 for ; Mon, 30 May 2011 21:18:23 +0000 (UTC) X-Greylist: delayed 01:10:01.417333 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 4DA41B603A1 for ; Mon, 30 May 2011 18:18:17 -0300 (ADT) Received: from mail.virtall.com (localhost [127.0.0.1]) by mail.virtall.com (Postfix) with ESMTP id 6E0BD363AD7; Mon, 30 May 2011 11:18:18 +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=mblnJHAUg PXBu9EOct3ieg+9Jaw=; b=qwOT7r8/geHriY9GFcjC8RaC05MeV/vO2EWIaJCOt Vvk3dO5TEsheBdf5n3XCBDS2PawnOF3EgheFWsuELRg4seE3VwbrI14rXbYGG6tC cTGS/Pzo9TyPIFRmi/GmpeaX4dafI9EX3aYZR7GBeDSx0dIvEmuZOwdR9MthnQ0N Xg= 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=fm4 Ia7mmv9dM+6NwuB0L4aPVoQ4mg4x2ppHDz0T+SvN8iNMBSMr6YeqdAL2vV31z6e+ DtjJntkzWg9efjLeHtCoUgLiixePOg+PN0afoKhpopHcB7AFKktEYjrj9vRsNVJk As4k1IDtxIgN8Jkq3gzfLXOzDL695fxiuz/Lmig4= Received: from [192.168.10.145] (e183095092.adsl.alicedsl.de [85.183.95.92]) by mail.virtall.com (Postfix) with ESMTPSA id 1468C363AD2; Mon, 30 May 2011 11:18:18 +0200 (CEST) Message-ID: <4DE360D9.5060300@wpkg.org> Date: Mon, 30 May 2011 11:18:17 +0200 From: Tomasz Chmielewski 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 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> <4DC1B6C0.2000507@wpkg.org> <4DC3B469.80004@wpkg.org> <4DC5B754.3040506@wpkg.org> In-Reply-To: <4DC5B754.3040506@wpkg.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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/179 X-Sequence-Number: 37616 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