Re: Vacuum return codes (vacuum as db integrity check?)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Stephane Charette" <stephanecharette(at)telus(dot)net>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Vacuum return codes (vacuum as db integrity check?)
Date: 2002-11-09 04:38:44
Message-ID: 288.1036816724@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Stephane Charette" <stephanecharette(at)telus(dot)net> writes:
> The error received when we run "vacuumdb" is:

> -> ERROR: Cannot insert a duplicate key into unique index
> pg_class_oid_index

That's pretty interesting. My first thought is a corrupt index.
Please try reindexing pg_class. You'll need to do this in a standalone
backend --- read the REINDEX reference page carefully.

> In our case, we are using 7.2 on a linux 2.2.14 kernel. Binaries were
> downloaded via RPM directly from RedHat.

7.2? You should be using 7.2.3.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message sachin deshpande 2002-11-09 15:04:14 unsuscribe
Previous Message Stephane Charette 2002-11-08 21:43:31 Re: Vacuum return codes (vacuum as db integrity check?)