Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B8E2B2E0091 for ; Mon, 10 Mar 2008 11:50:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 76583-09 for ; Mon, 10 Mar 2008 11:50:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 8D9112E006F for ; Mon, 10 Mar 2008 11:50:24 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m2AEnsP6023798; Mon, 10 Mar 2008 10:49:56 -0400 (EDT) To: tony@altonet.co.za cc: pgsql-admin@postgresql.org Subject: Re: problem with pg_statistic_relid_att_index In-reply-to: <20080310125732.332572E014D@postgresql.org> References: <20080310125732.332572E014D@postgresql.org> Comments: In-reply-to "Tony Da Silva" message dated "Mon, 10 Mar 2008 14:57:23 +0200" Date: Mon, 10 Mar 2008 10:49:54 -0400 Message-ID: <23797.1205160594@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/77 X-Sequence-Number: 28560 "Tony Da Silva" writes: > When I log into pgsql I see this: > ERROR: Invalid page header in block 3 of pg_statistic_relid_att_index I can't think of any reason that a simple connection attempt would be trying to read pg_statistic. Perhaps you have some nontrivial query in your ~/.psqlrc? If so try taking that out. If that doesn't work you might have to resort to setting zero_damaged_pages in postgresql.conf, but that's a pretty dangerous tool --- it might zap pages you weren't expecting it to. Don't keep it on any longer than you absolutely have to. Once you do get into the DB you should be able to just REINDEX pg_statistic to fix the problem. (In 7.3 you might have to use a standalone backend for that, I don't recall for sure.) > Welcome to psql 7.3.4, the PostgreSQL interactive terminal. Egad. You do know that 7.3 was up to 7.3.21 before we obsoleted it? If your DB is unrecoverable because of some data-eating bug that was fixed in the past four-plus years, you're not going to get a lot of sympathy. regards, tom lane