[postgis-tickets] [PostGIS] #3675: Relationship functions not using an index in some cases

[PostGIS]

#3675: Relationship functions not using an index in some cases
----------------------+---------------------------
  Reporter:  robe     |      Owner:  robe
      Type:  defect   |     Status:  new
  Priority:  blocker  |  Milestone:  PostGIS 2.3.2
 Component:  postgis  |    Version:  2.3.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 I'm definitely becoming more dyslexic, I labeled the commit # wrong on
 last commit. Should have gone to this one.

 In [changeset:"15280" 15280]:
 {{{
 #!CommitTicketReference repository="" revision="15280"
 Relationship functions not using an index in some cases
 Set cost back to 1 for functions that return a geometry
 A higher cost has the side-effect of making the planner
 think when used in conjunction with relate constructs like ST_Intersects
 it's cheaper to compute the geometry once rather
 than compute twice and break into an index and non-index call.
 References #3657 for PostGIS 2.3
 }}}

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3675#comment:11>
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.