[postgis-tickets] [PostGIS] #3739: ST_Within Not using index

[PostGIS]

#3739: ST_Within Not using index
--------------------------+---------------------------
  Reporter:  postgispaul  |      Owner:  pramsey
      Type:  defect       |     Status:  new
  Priority:  medium       |  Milestone:  PostGIS 2.3.3
 Component:  postgis      |    Version:  2.3.x
Resolution:               |   Keywords:
--------------------------+---------------------------
Changes (by robe):

 * cc: pramsey (added)


Comment:

 Not sure.  Gist indexes have always caused us problems on tables where we
 always need to do massive updates e.g. where we get new electronic updated
 info from a vendor that requires us to update more than 20%-30% of a
 table.

 A lot of the fixes I've seen for example in 9.6.2 (haven't checked 9.6.3
 upcoming list) had to do with how the planner handles parallel queries.
 Anyway I think I've got a freebsd box lying around (PostgreSQL 9.3 with
 2.3.something) somewhere that has full osm data loaded (or full enough)
 and see if I can replicate.

 It's odd that && doesn't give the same issue as ~ as those look like they
 have similar costs and should go down similar channels. I would think with
 a corrupt index it would suffer the same fate.

 pramsey any thoughts on this one?

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3739#comment:4>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.