X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BE5D4D6E26 for ; Fri, 9 Sep 2005 12:08:12 -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 10277-10 for ; Fri, 9 Sep 2005 15:08:07 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 744B9D839E for ; Fri, 9 Sep 2005 12:08:06 -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 j89F7rDi010711; Fri, 9 Sep 2005 11:07:54 -0400 (EDT) To: Dilipan Sebastiampillai Cc: pgsql-admin@postgresql.org Subject: Re: could not locate a valid checkpoint record In-reply-to: <4321996C.90603@framestore-cfc.com> References: <4321996C.90603@framestore-cfc.com> Comments: In-reply-to Dilipan Sebastiampillai message dated "Fri, 09 Sep 2005 15:17:16 +0100" Date: Fri, 09 Sep 2005 11:07:53 -0400 Message-ID: <10710.1126278473@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200509/96 X-Sequence-Number: 18833 Dilipan Sebastiampillai writes: > I tried ( after copying thes PGDATA dir obviously ) : > pg_resetxlog /var/lib/pgsql/data/ -f > After that postgreSQL starts but I realised that pg_database is empty ( > it contains only template0 and template1 ) . It sounds like pg_resetxlog guessed at an XID counter that is too small and so all your data rows seem to be "in the future". You need to find out approximately where the XID counter had been. You can probably tell this by looking at the pg_clog directory; read the pg_resetxlog man page for details. I would suggest paying close attention to the other settable options for resetxlog, too --- if it got XID wrong then it likely got the others wrong as well. Once you get out of this I'd suggest a dump/initdb/restore to make sure your data is consistent; you may well have more problems than appear on the surface. Oh, and updating to the latest release of the 7.4 branch would be a good idea too ;-). There are some pretty serious known bugs in 7.4.5. regards, tom lane