From: | Nathan Robertson <nathan(dot)robertson(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: cache lookup failed for index |
Date: | 2010-06-30 16:19:18 |
Message-ID: | AANLkTim5VFISQ6IVRrtmy9dr1aRJb5fu7n_LUmTVDkak@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks Tom.
OK, I ran:
postgres -O -P -D /cluster/location
reindex table pg_class;
backend> reindex table pg_class;
And then nothing returns. Nothing stating whether it was successful or a
failure.
And then if I do:
bash-3.2$ postgres -O -P -D /shared/webapp/database webapp
I still get:
FATAL: cache lookup failed for index 2662
On Wed, Jun 30, 2010 at 12:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-30 17:04:59 | Re: cache lookup failed for index |
Previous Message | Tom Lane | 2010-06-30 16:14:23 | Re: cache lookup failed for index |