[postgis-tickets] [PostGIS] #2898: Define a guideline for function cost

[PostGIS]

#2898: Define a guideline for function cost
-------------------------+--------------------------------------------------
 Reporter:  strk         |       Owner:  pramsey      
     Type:  enhancement  |      Status:  new          
 Priority:  medium       |   Milestone:  PostGIS 2.2.0
Component:  postgis      |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------

Comment(by strk):

 Alright so in the light of the new findings, sliced detoasting (header
 only) and full detoasting do not make such a big difference. It is
 detoasting itself that hurts. Guidelines should then not take that part
 much in consideration, other than a COST offset common to each and every
 function.

 Besides, I suspect that the planner should be considering cost of
 detoasting on itself, as the same function could be invoked with the input
 already detoasted...

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