Changes between Initial Version and Version 14 of Ticket #230


Ignore:
Timestamp:
Aug 8, 2009, 11:27:36 PM (15 years ago)
Author:
robe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #230

    • Property Status newassigned
    • Property Summary st_expand seems to affect the execution order wich affects st_dwithinPut in costs in _ST and possibly other functions
    • Property Version1.4
    • Property Owner changed from pramsey to robe
  • Ticket #230 – Description

    initial v14  
     1I'm revising this since this seems to be an issue mostly because we don't have COSTS assigned to our _ST functions, so the planner in certain cases (like with large geometries), chooses to do a table scan instead of an index scan.
     2
     3Since costs are only supported in PostgreSQL 8.3+ and we are also going to need typmod support for geography.  I'm wondering if we want to just push this to 1.5 and also make PostgreSQL 8.3+ a requirement for 1.5 instead of introducing messy conditional code to not put costs in if 8.2 or lower.
     4
     5----OLD description
     6
    17using dataset from states.backup as example
    28