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 A7B7553466 for ; Mon, 2 May 2005 11:53:06 -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 10500-03 for ; Mon, 2 May 2005 14:53:01 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 66E0D54428 for ; Mon, 2 May 2005 11:52:56 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j42Eqljf018386; Mon, 2 May 2005 10:52:48 -0400 (EDT) To: Mauri Sahlberg Cc: pgsql-admin@postgresql.org Subject: Re: A nightmare In-reply-to: <1115014768.8003.9.camel@localhost.localdomain> References: <1115014768.8003.9.camel@localhost.localdomain> Comments: In-reply-to Mauri Sahlberg message dated "Mon, 02 May 2005 09:19:28 +0300" Date: Mon, 02 May 2005 10:52:47 -0400 Message-ID: <18385.1115045567@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200505/7 X-Sequence-Number: 17436 Mauri Sahlberg writes: > I'm starting to become desperate. On saturday I dumped all databases, > wiped whole postgresql installation. Installed newest rpms for Fedora 1, > restored databases. Recompiled client libraries and binaries. Restarted > and after five hours of operation: > May 1 21:34:19 claymountain postgres[6337]: [2-1] ERROR: could not > access status of transaction 4250811410 > May 1 21:34:19 claymountain postgres[6337]: [2-2] DETAIL: could not > open file > "/var/lib/pgsql/data/pg_clog/0FD5": No such file or directory Which exactly are the "newest rpms for Fedora 1" ... what PG version and where did you get them from? > Is there anything else I could do than dump, wipe, restore again? Isn't > there anything I could do to try to get more detailed meaningful > information on why this is happening? It looks like a corrupt-data issue to me. You could follow the usual sorts of procedures to try to isolate and get rid of the bad data (see the list archives for details). But I think first you need to question what caused it. Could your disk drive be failing (or other hardware problem)? How much do you trust the specific kernel version you are currently running? regards, tom lane