Re: dupes for PK and other UNIQUE indexes - Mailing list pgsql-admin

From Kevin Kempter
Subject Re: dupes for PK and other UNIQUE indexes
Date
Msg-id 200911011630.14903.kevink@consistentstate.com
Whole thread Raw
In response to Re: dupes for PK and other UNIQUE indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
On Sunday 01 November 2009 16:25:58 Tom Lane wrote:
> Kevin Kempter <kevink@consistentstate.com> writes:
> > On Sunday 01 November 2009 15:50:20 you wrote:
> >> Kevin Kempter <kevink@consistentstate.com> writes:
> >>> Anyone have any Idea how this could happen?
> >>
> >> Corrupt indexes.  What PG version are we talking about?
> >
> > version 8.3.8
>
> Well, there aren't any known causes of btree index corruption in 8.3.x,
> but that doesn't mean you haven't found something new.  Does this
> installation have any nonstandard history?  (I'm wondering about things
> like it having been a WAL standby at one time, or part of a Slony
> setup, or something like that.)  Can you provide any other data that
> might help somebody reproduce the problem?
>
> BTW, please keep your responses cc'd to the list.
>
>             regards, tom lane
>

I'll do some digging and see what I can find. They are using Ruby on Rails,
that's all I have so far.



pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: dupes for PK and other UNIQUE indexes
Next
From: Dhaval Rami
Date:
Subject: Postgresql 8.4 and Data warehousing