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 5338C8BB071 for ; Mon, 21 Feb 2005 16:42:10 +0000 (GMT) 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 32192-02 for ; Mon, 21 Feb 2005 16:42: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 CD0938BB065 for ; Mon, 21 Feb 2005 16:42:07 +0000 (GMT) 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 j1LGg6La000633; Mon, 21 Feb 2005 11:42:06 -0500 (EST) To: "Anjan Dave" Cc: pgsql-admin@postgresql.org Subject: Re: pg_clog corrupt, can't start postgres In-reply-to: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509881E@vt-pe2550-001.vantage.vantage.com> References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509881E@vt-pe2550-001.vantage.vantage.com> Comments: In-reply-to "Anjan Dave" message dated "Mon, 21 Feb 2005 10:58:16 -0500" Date: Mon, 21 Feb 2005 11:42:06 -0500 Message-ID: <632.1109004126@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: 200502/194 X-Sequence-Number: 16362 "Anjan Dave" writes: > The partition ran out of space from an import process. I cleared up the space and attempted to start the postgres service again, but it doesn't start and i get following in the message log. > PANIC: could not access status of transaction 45514755 > DETAIL: could not read from file "/var/lib/pgsql/data/pg_clog/002B" at offset 106496: Success > LOG: startup process (PID 23991) was terminated by signal 6 > LOG: aborting startup due to startup process failure > Postgres is 7.4.1 on this machine. > I saw some previous posts on this subject and so far the solution seems to be initialize and restore databases from the dumps. Before that, try updating to 7.4.7 (or at least 7.4.2) --- this looks like the same bug fixed here: 2004-01-26 14:16 tgl * src/backend/access/transam/varsup.c (REL7_4_STABLE): Repair incorrect order of operations in GetNewTransactionId(). We must complete ExtendCLOG() before advancing nextXid, so that if that routine fails, the next incoming transaction will try it again. Per trouble report from Christopher Kings-Lynne. You might also go back to the mail list archives from that time and see what advice was given to Chris about getting out of the problem he found himself in. I *think* that something along the line of forcibly appending a page of zeroes to that clog file might be the best solution, but this was more than a year ago and I don't recall for sure. regards, tom lane