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 26E62D1B181 for ; Thu, 1 Jul 2004 20:39:17 -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 63771-01 for ; Thu, 1 Jul 2004 23:39:11 +0000 (GMT) Received: from bluff.diade.it (adsl-161-130.38-151.net24.it [151.38.130.161]) by svr1.postgresql.org (Postfix) with ESMTP id A11E9D1B170 for ; Thu, 1 Jul 2004 20:39:06 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by bluff.diade.it (Postfix) with ESMTP id 495571AAC2; Fri, 2 Jul 2004 01:39:04 +0200 (CEST) Received: from bluff.diade.it ([127.0.0.1]) by localhost (bluff [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02105-07; Fri, 2 Jul 2004 01:39:02 +0200 (CEST) Received: by bluff.diade.it (Postfix, from userid 500) id 8D8271C386; Fri, 2 Jul 2004 01:39:02 +0200 (CEST) Date: Fri, 2 Jul 2004 01:39:02 +0200 From: Sandro Dentella To: Sandro Dentella , pgsql-admin@postgresql.org Subject: Re: pg_clog error after crash Message-ID: <20040701233902.GA3829@bluff> References: <20040630155919.GA3174@bluff> <6331.1088719517@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6331.1088719517@sss.pgh.pa.us> User-Agent: Mutt/1.5.6+20040523i X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at e-den.it 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/97 X-Sequence-Number: 14165 On Thu, Jul 01, 2004 at 06:05:17PM -0400, Tom Lane wrote: > 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...) No, really I could connect to the database that had probles! I could "COPY table TO 'file' for *each* table of the problematic db. The problem arouse when trying to pg_dump it or when trying to access it via libpgtcl (I use TkSQL as you can guess from the footer ;-). After COPYing all tables I created the file that was missing, filled with zeros according to a mail I found of a "similar" problem. PostgreSQL complain disappeard. As far as I can say no data seems to be lost. I'm using PostgreSQL 7.4.2 last release of Debian Sarge. Thanks for your time. sandro *:-) -- Sandro Dentella *:-) e-mail: sandro@e-den.it http://www.tksql.org TkSQL Home page - My GPL work