Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 68388632A04
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 30 Jun 2010 13:14:32 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 51341-07 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 30 Jun 2010 16:14:25 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 526096329C7
	for <pgsql-admin@postgresql.org>; Wed, 30 Jun 2010 13:14:25 -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 o5UGENOR011713;
	Wed, 30 Jun 2010 12:14:23 -0400 (EDT)
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
cc: "Nathan Robertson" <nathan.robertson@gmail.com>,
 pgsql-admin@postgresql.org
Subject: Re: cache lookup failed for index 
In-reply-to: <4C2B21A00200002500032D8D@gw.wicourts.gov> 
References: <AANLkTilzUWnxCjomBRHkByi6tHeS8fDIRNqvU9WCsv1G@mail.gmail.com>
	<4C2B02040200002500032D63@gw.wicourts.gov>
	<AANLkTikYlHg1mVytsX_QQWSf58MTrw-aTIklyv5Zh2KY@mail.gmail.com>
	<4C2B0AEF0200002500032D75@gw.wicourts.gov>
	<AANLkTilfWzYJTo7J39shOutT9bvM9tyxAYa1ZI1rkWeT@mail.gmail.com>
	<4C2B21A00200002500032D8D@gw.wicourts.gov>
Comments: In-reply-to "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
	message dated "Wed, 30 Jun 2010 10:51:12 -0500"
Date: Wed, 30 Jun 2010 12:14:23 -0400
Message-ID: <11712.1277914463@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201006/221
X-Sequence-Number: 34999

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> OK, I think the appropriate next step would be to try to run the
> PostgreSQL cluster in single-user mode:
 
> http://www.postgresql.org/docs/8.1/interactive/app-postgres.html
 
> Try to REINDEX pg_class_oid_index in that mode.  If that fails, it
> might possibly help to run these statements and try the REINDEX
> command again:
 
> set enable_indexscan = off;
> set enable_bitmapscan = off;

Those won't help.  What you *will* need, in order to even start the
single-user backend, is to tell it to disregard system indexes
(-P command line option).

I wouldn't be too surprised if the corruption extends a lot further than
the one index :-( but maybe you will be able to extract something after
reindexing.

			regards, tom lane