From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Silvela, Jaime \(Exchange\)" <JSilvela(at)Bear(dot)com> |
Cc: | "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Can't open Postgres at all!!! |
Date: | 2006-08-24 13:06:02 |
Message-ID: | 3292.1156424762@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Silvela, Jaime \(Exchange\)" <JSilvela(at)Bear(dot)com> writes:
> I just came back this morning after doing a REINDEX of pg_class
> Nothing is working. I try to REINDEX pg_class and it complains
> ERROR: could not open relation 1663/16390/2662: No such file or
> directory
If the index entries for the system catalogs themselves are hosed,
you may have to start the session with PGOPTIONS="-P" (to disable
trusting system indexes) in order to do REINDEX successfully.
However, there is zero point in doing any repair work until you have a
stable hardware platform to do it on, so I'd get after the hardware
problem first. The longer you run the database with the current
degree of instability, the more likely you are to have some corruption
in table pages rather than index pages ... and a simple REINDEX won't
get you out of that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Silvela, Jaime (Exchange) | 2006-08-24 13:14:54 | Re: Can't open Postgres at all!!! |
Previous Message | Emi Lu | 2006-08-24 12:59:10 | Length limit for query |