Re: 3rd time is a charm.....right sibling is not next child crash.

On 6/8/10 2:03 PM, "Alvaro Herrera" <alvherre@commandprompt.com> wrote:

> 
> I've seen this problem (and others) in a high-load environment.  Not
> Slony related though.
> 
> I wrote a small tool to check btree index files for consistency problems
> such as this one, by parsing pg_filedump output.  I've seen strange
> things such as index pointers pointing to pages that shouldn't have been
> pointed to; mismatching sibling pointers; and others.
> 
> Do you have a copy of the broken index file?

Alas, no.  But I have another 5 days to reproduce the problem before
changing hardware/versions (which will probably bring a whole new set of
'opportunities' to deal with).  If it happens again, I will snag the index
file for analysis.

Any way you can share your tool source so I can proactively look for issues
in my indexes?