From: | "John Lister" <john(dot)lister-ps(at)kickstone(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: database corruption help |
Date: | 2009-02-09 19:20:40 |
Message-ID: | AB15E89CD7FB4EBD9D76CC5F8D8B3D4E@squarepi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Cheers tom, that did it - i've removed the duplicates and seeing what else
is broken.
.
> "John Lister" <john(dot)lister-ps(at)kickstone(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-02-09 19:34:04 | Re: database corruption help |
Previous Message | Stefano Nichele | 2009-02-09 17:43:43 | strange autovacuum behaviour |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-02-09 19:34:04 | Re: database corruption help |
Previous Message | Tom Lane | 2009-02-09 18:59:45 | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |