From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Nathan Robertson" <nathan(dot)robertson(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: cache lookup failed for index |
Date: | 2010-06-30 16:14:23 |
Message-ID: | 11712.1277914463@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"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 | Nathan Robertson | 2010-06-30 16:19:18 | Re: cache lookup failed for index |
Previous Message | Kevin Grittner | 2010-06-30 16:13:21 | Re: cache lookup failed for index |