Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id D760C1337B69 for ; Wed, 4 May 2011 03:21:45 -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 75385-03 for ; Wed, 4 May 2011 06:21:26 +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 62D4E13364DE for ; Wed, 4 May 2011 03:21:26 -0300 (ADT) Received: from mail.virtall.com (localhost [127.0.0.1]) by mail.virtall.com (Postfix) with ESMTP id 6009636222E for ; Wed, 4 May 2011 08:21:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=wpkg.org; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; s=default; bh=m9uIhiEHxYqWW3+VqS24/J qJuWw=; b=32+SivHT9VbBv7Zx0Z6u83ElUj10PbJUPb7tIv0S0jk2Yb3wOUDCZe gYEUKFawuKqxMBFzBH1b6EccXxg9TGtPLZxXDlNcX/rTOgqwW++O1UPWLv20jeAE MoBfHfyjxBYp7l8QeunruQklLR+75UCsTJCQjP788QjA9FCMHpaWw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=wpkg.org; h=message-id:date :from:mime-version:to:subject:content-type :content-transfer-encoding; q=dns; s=default; b=Wlfxgo+9743L/jK9 4SzJhctcp+k3XxzWGOyX8NE9o65gxIl4qPZut1ZX6gIDtTn6kL346qIPz9rR8YKt OB2pPskUN0SPVxW1WoTUaGRZneQUNS2M1jwGO9AfjZMvZDbAb25+z71KSz/dVP0o HOWmL3XDPCP/9cXMkD9Kdv3D5rc= Received: from [192.168.10.145] (e183095092.adsl.alicedsl.de [85.183.95.92]) by mail.virtall.com (Postfix) with ESMTPSA id CA8783620E7 for ; Wed, 4 May 2011 08:21:23 +0200 (CEST) Message-ID: <4DC0F063.70306@wpkg.org> Date: Wed, 04 May 2011 08:21:23 +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: pgsql-admin@postgresql.org Subject: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now? Content-Type: text/plain; charset=UTF-8; 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/35 X-Sequence-Number: 37472 On 1st May, I saw this message in my postgres log: May 2 06:52:02 db10 postgres[3590]: [29829-1] 2011-05-02 06:52:02 SGT ERROR: could not access status of transaction 1573786613 May 2 06:52:02 db10 postgres[3590]: [29829-2] 2011-05-02 06:52:02 SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory. May 2 06:52:02 db10 postgres[3590]: [29829-3] 2011-05-02 06:52:02 SGT STATEMENT: SELECT 1 FROM core_bill_id_seq FOR UPDATE Now, I'm not sure what I should do about it. Database behaves "funny", some inserts do not work. Searching the internet suggests that: 1) such errors could happen with PostgreSQL 8.1.x under heavy load - this server is under constant heavy load, but runs 8.3.14 on Debian Lenny 2) I should simply create a 256k pg_clog/05DC empty file with dd - I wouldn't like to do it, without first knowing what happened, and if it's really "good fix" 3) some tables can be corrupted - how can I check that? pg_dump works fine and doesn't report any errors 4) I may have hardware problems - but this server is running for almost 1 year now, is super stable - servers with hardware issues are likely to show some issues as well 5) database corrupted due to a server crash - this server never crashed How should I continue from that (assuming I can't reliably verify if something wrong is going with the hardware or not - points 4 and 5)? -- Tomasz Chmielewski http://wpkg.org