| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Kempter <kevink(at)consistentstate(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: dupes for PK and other UNIQUE indexes |
| Date: | 2009-11-01 23:25:58 |
| Message-ID: | 2779.1257117958@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Kevin Kempter <kevink(at)consistentstate(dot)com> writes:
> On Sunday 01 November 2009 15:50:20 you wrote:
>> Kevin Kempter <kevink(at)consistentstate(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Kempter | 2009-11-01 23:30:14 | Re: dupes for PK and other UNIQUE indexes |
| Previous Message | Tom Lane | 2009-11-01 22:50:20 | Re: dupes for PK and other UNIQUE indexes |