Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 551FA9F9509 for ; Sun, 4 Nov 2007 11:54:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 80536-04 for ; Sun, 4 Nov 2007 11:53:45 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 841269F94F6 for ; Sun, 4 Nov 2007 11:54:04 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lA4Fs0NM013870; Sun, 4 Nov 2007 10:54:00 -0500 (EST) To: Alexander Lohse cc: pgsql-admin@postgresql.org Subject: Re: Problems with missing OIDs In-reply-to: References: <043A7BA3-8C72-4D9C-B7DD-52B183A2B313@humantouch.de> <11596.1194109249@sss.pgh.pa.us> Comments: In-reply-to Alexander Lohse message dated "Sun, 04 Nov 2007 11:51:22 +0100" Date: Sun, 04 Nov 2007 10:54:00 -0500 Message-ID: <13869.1194191640@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/41 X-Sequence-Number: 27284 Alexander Lohse 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