[postgis-devel] [PostGIS] #1165: Selectivity extimation of && operator

[PostGIS]

#1165: Selectivity extimation of && operator
----------------------------+-----------------------------------------------
 Reporter:  edoardopanfili  |       Owner:  pramsey      
     Type:  defect          |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 1.5.4
Component:  postgis         |     Version:  1.5.X        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by robe):

 Edoardo,
 join selectivity with LEFT JOINs is a known issue.  FULL JOINS on a
 spatial function aren't supported at all.  As far as the join selectivity
 issues, I'll let Paul or Mark comment on those since I'm not sure how all
 that works.  I do know I've had a lot of selectivity issues (particularly
 with tiger geocoder) which I have worked around by using WITH queries to
 control the plan as you have. I wasn't really sure where to put the blame
 since a lot of those were just plain attribute queries.

 I am more concerned about your 2.0 issues.  Which subversion revision
 number are you using of PostGIS 2.0?  Are the plans the same as on your
 1.5?  Is your 2.0 installed on the same version of PostgreSQL as your 1.5?

 I've loaded a couple of my production databases using PostGIS 2.0 (about
 2-3 week old release on Windows), and haven't noticed any major noticeable
 differences.  Some things are a slower but not by much and some things are
 faster (which seems to be more to do with the higher accuracy of the
 bounding box in 2.0)

 Regina

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1165#comment:1>
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.