From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Lohse <al@humantouch.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: Problems with missing OIDs
Date: Sun, 04 Nov 2007 10:54:00 -0500
Message-ID: <13869.1194191640@sss.pgh.pa.us> (raw)
In-Reply-To: <BF753DE5-D0C3-4AC5-972F-C22999009BC1@humantouch.de>
References: <043A7BA3-8C72-4D9C-B7DD-52B183A2B313@humantouch.de>
<11596.1194109249@sss.pgh.pa.us>
<BF753DE5-D0C3-4AC5-972F-C22999009BC1@humantouch.de>
Alexander Lohse <al@humantouch.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, al@humantouch.de
Subject: Re: Problems with missing OIDs
In-Reply-To: <13869.1194191640@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox