From: | Dylan Adams <dylan(dot)adams(dot)work(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Index Corruption |
Date: | 2011-09-12 18:10:26 |
Message-ID: | CA+Rt69bt4M6hHWDhMGKi=5BqyaaoCwjDTYZmk+RQ-Uwwgfe=yw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Sep 12, 2011 at 9:41 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dylan Adams <dylan(dot)adams(dot)work(at)gmail(dot)com> writes:
>> [ persistent occurrences of index corruption ]
>
>> My primary question: is this normal?
>
> No. It does sound like you're managing to tickle some bug or other.
> Can you extract a test case of any kind? We could fix it if we could
> see it happening, but there's not enough information here for that.
I haven't been able to come up with a self contained test case.
There have been a few instances where a particular series of batch
processes which, when run repeatedly on a particular data set, will
reproduce the problem consistently. But it's not possible to release
the required code and data.
dylan
From | Date | Subject | |
---|---|---|---|
Next Message | Dylan Adams | 2011-09-12 18:12:09 | Re: Index Corruption |
Previous Message | Grzegorz Jaśkiewicz | 2011-09-12 16:32:03 | Re: 8.4.4 locked after power failure |