[postgis-devel] [PostGIS] #1024: Change 3D relationship functions to use &&& instead of &&

[PostGIS]

#1024: Change 3D relationship functions to use &&& instead of &&
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  pramsey      
     Type:  task     |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.0.0
Component:  postgis  |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by nicklas):

 As seen in the attached .sql the planner didn't react as I had hoped.

 It looks at the &&& operator and judge it as more expensive than &&
 operator.

 Is there a "cost" somewhere? I didn't see it.

 In the example in the file with 100000 records the planner chooses a heap
 bit scan if it is forced to use &&& operator. If it can chose it uses an
 index scan on the && operator and ignores the &&& operator.

 Interesting is that if I increase the number of records to 1000000, then
 it uses a hep bit scan also with && operator but still chooses && over &&&
 operator.

 I really hope there is a cost somewhere to tweak. Or is it just doing
 those decisions from statistics?

 /Nicklas

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