"Kevin Grittner" <[email protected]> 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
--
Sent via pgsql-admin mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
