Changes between Initial Version and Version 14 of Ticket #230
- Timestamp:
- 08/08/09 23:27:36 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #230
- Property Version → 1.4
- Property Owner changed from to
- Property Status new → assigned
- Property Summary st_expand seems to affect the execution order wich affects st_dwithin → Put in costs in _ST and possibly other functions
-
Ticket #230 – Description
initial v14 1 I'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 3 Since 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 1 7 using dataset from states.backup as example 2 8