Message-ID: <AB15E89CD7FB4EBD9D76CC5F8D8B3D4E@squarepi.com>
From: "John Lister" <john.lister-ps@kickstone.com>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: <pgsql-admin@postgresql.org>
References: <507152DDF8AB4DF093BD01A8BEC7C659@squarepi.com>
	<17205.1234200693@sss.pgh.pa.us>
Subject: Re: database corruption help 
Date: Mon, 9 Feb 2009 19:20:40 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

Cheers tom, that did it - i've removed the duplicates and seeing what else 
is broken.

.


> "John Lister" <john.lister-ps@kickstone.com> writes:
>> ERROR:  could not create unique index "pg_class_oid_index"
>
>> a quick inspection of the pg_class table doesn't show any duplicates, is 
>> there anyway i can find out which row(s) are duplicated and remove them 
>> without a full db restore?
>
>> also doing something like this doesn't return anything which worked for 
>> my other tables
>
>> select oid from pg_class where oid in(select oid from pg_class group by 
>> oid having count(oid)>1 )
>
> Try doing it with enable_indexscan = off and enable_bitmapscan = off.
> The system might be relying on the old, bogus index to do the group by
> oid.
>
> regards, tom lane
>