X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6060BD1B4F9 for ; Thu, 1 Jul 2004 19:05:24 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 17074-06 for ; Thu, 1 Jul 2004 22:05:25 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 46774D1B46A for ; Thu, 1 Jul 2004 19:05:20 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i61M5HlL006332; Thu, 1 Jul 2004 18:05:17 -0400 (EDT) To: Sandro Dentella Cc: pgsql-admin@postgresql.org Subject: Re: pg_clog error after crash In-reply-to: <20040630155919.GA3174@bluff> References: <20040630155919.GA3174@bluff> Comments: In-reply-to Sandro Dentella message dated "Wed, 30 Jun 2004 17:59:19 +0200" Date: Thu, 01 Jul 2004 18:05:17 -0400 Message-ID: <6331.1088719517@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/25 X-Sequence-Number: 14093 Sandro Dentella writes: > After a crash of the (frozen) system, postgreSQL issues a message: > 2004-06-30 17:51:39 [3165] LOG: connection authorized: user=sandro database=sia > 2004-06-30 17:51:39 [3165] ERROR: could not access status of transaction 4011600129 > DETAIL: could not open file "/var/lib/postgres/data/pg_clog/0EF1": No such file or directory It looks like you've got data corruption in one of the system catalogs that is accessed during backend startup. This is not good :-(. Do you get the same no matter which of the databases in your installation you try to connect to? (Not that it will matter much, if all your important data is in this database...) You may have little choice but to restore from your last backup. regards, tom lane