From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alexander Lohse <al(at)humantouch(dot)de> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Problems with missing OIDs |
Date: | 2007-11-04 15:54:00 |
Message-ID: | 13869.1194191640@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Alexander Lohse <al(at)humantouch(dot)de> writes:
>> That really shouldn't have happened in the first place. Are you
>> running
>> an up-to-date Postgres version? Are you sure your disk drives don't
>> lie
>> about write completion?
> the server is running PostgreSQL 7.4. The disks where replaced by our
> hosting partners, so I do not know anything about their internal state.
7.4.what?
> The index for a primary key contstraint on that table is missing.
> I also cannot drop and recreate that constraint!
> Can I just go ahead and drop the corresponding rows from pg_contraint
> and pg_index?
Yeah, what you'll have to do is remove individual rows from the catalogs
until you can get pg_dump to run without error. Then reload into a
fresh database and check for signs of inconsistency, missing data or
tables, etc.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Goldner | 2007-11-04 22:49:13 | Database size with large objects |
Previous Message | Alexander Lohse | 2007-11-04 10:51:22 | Re: Problems with missing OIDs |