> Yeah, but the update case is inserting more entries into the index.
> I'm wondering if that causes the index scan's state to get corrupted
> so that it misses scanning some entries. btree has a carefully designed
> algorithm to cope with this, but I have no idea how gist manages it.
Thank you, Tom. You give me a direction for looking. Attached patch fix
the problem with broken state. Please apply it for 7.2.2 and current cvs
(sorry,
but I'll have a possibility to check it on current cvs only tomorrow).
--
Teodor Sigaev
teodor@stack.net