[postgis-devel] [PostGIS] #230: Put in costs in _ST and possibly other functions
PostGIS
trac at osgeo.org
Mon Aug 10 00:11:57 PDT 2009
#230: Put in costs in _ST and possibly other functions
----------------------+-----------------------------------------------------
Reporter: nicklas | Owner: robe
Type: defect | Status: assigned
Priority: medium | Milestone: postgis 1.5.0
Component: postgis | Version: 1.4
Resolution: | Keywords: st_dwithin st_expand bbox
----------------------+-----------------------------------------------------
Comment (by robe):
Nicklas,
Very Good idea. I like the idea of keeping the costs in a separate file.
That way if people decide they want different costs for their functions,
they can simply just not run that file. However -- I still want to get
rid of 8.2, just from a keeping my sanity point of view. I would like it
that at any point in time, we only need to test at most 2 versions of
PostgreSQL for new features. Trying to remember what we can and can't do
for 2 versions is enough without having to worry about a third. Now we
have 8.3 and 8.4 and 8.5 has already started their cycle -- so we'll want
to start testing out 8.5 in probably another 3-4 months (or less).
I'm not saying we won't support 8.2. we just shouldn't support it for 1.5
and beyond. I still expect we will support 1.4, 1.3 for years to come,
but that support will just be security fixes and major bug fixes that
could corrupt data.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/230#comment:18>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS
More information about the postgis-devel
mailing list