Dave Cramer <pg@fastcrypt.com> writes:
> Ok, that seems to have fixed it, so my next question is how did it get
> corrupt?
The nearest culprit seems to be whatever you did in analyze.c ;-). It's
not obvious to me how analyze.c would manage to mess up an index, since
it's nowhere near the index-handling code, but I'd sure want to examine
your patch before looking further afield for an explanation.
regards, tom lane