Stephen Davies wrote:
I have finally resolved this issue by upgrading to 8.3.6 and then dropping and
recreating the relevant GIST geometry index.
Could this be a manifestation of the GIST bug fixed in 8.3.6?
Cheers,
Stephen
Possibly. I believe the bug was that some kind of state variable was not
being set at the start of an index scan, which would affect tuple
visibility.
ATB,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
