> I will patch this in both current and REL6_5. But, although this
> is clearly a bug, I am not at all convinced that it explains
> Adriaan's problem. I think more creepie-crawlies lurk nearby :-(
Hmm, I made the changes and I only got three errors out of the system
today. So it is not fixed, although perhaps improved (or was I just
lucky?). I've been locking tables more restrictively, so this may have
helped as well. I definitely think this has something to do with
concurrent accesses to the same index. It always seems to start
happening as the the tables start getting updates more rapidly.
Another thought: an index on a table that gets updated sometimes through
a PL trigger is an index on a user-defined type (the bitmask type I
posted a while ago). Could this have something to do with a btree index
on a user-defined type? I'll drop that index and see whether it makes a
difference. All indexes on other tables that are touched are int4.
Thanks for all the help, Tom!
Adriaan