[postgis-users] Broken r-tree semantics

[strk at refractions.net]

Hello users!

Reference:
http://archives.postgresql.org/pgsql-hackers/2005-06/msg01108.php

A bug in r-tree semantics has been found and fixed.
We ported the fix to postgis, which is also affected by
it. Basically in some cases an index scan would fail
catching some records that would be coutch by a
sequential scan. 

Now:
- Do you think it's worth porting the patch to the 0.9 branch ?
- Did anyone experienced this problem ?

--strk;