Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id F185D64FC0D for ; Tue, 23 Sep 2008 23:42:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 86688-08 for ; Tue, 23 Sep 2008 23:42:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 70DA064FC15 for ; Tue, 23 Sep 2008 23:42:20 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m8O2gGQ4017343; Tue, 23 Sep 2008 22:42:16 -0400 (EDT) To: Carol Walter cc: pgsql-admin@postgresql.org Subject: Re: error In-reply-to: References: Comments: In-reply-to Carol Walter message dated "Tue, 23 Sep 2008 16:48:35 -0400" Date: Tue, 23 Sep 2008 22:42:16 -0400 Message-ID: <17342.1222224136@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/267 X-Sequence-Number: 30360 Carol Walter writes: > What would cause this error? > ERROR: could not access status of transaction 10274530 > DETAIL: Could not open file "pg_clog/0009": No such file or directory. We've seen that caused by bugs that made Postgres throw away clog files too soon; but as far as I know those bugs were all squashed in recent releases. What PG version is this? What files *are* present in pg_clog, and what are their mod times? Have you had any system crashes recently? regards, tom lane