[postgis-tickets] [PostGIS] #2659: extension upgrade from 2.1.2dev to 2.2.0dev fails with st_countagg(raster, integer, boolean, double precision) does not exist
PostGIS
trac at osgeo.org
Thu Jun 19 06:24:17 PDT 2014
#2659: extension upgrade from 2.1.2dev to 2.2.0dev fails with
st_countagg(raster,integer,boolean,double precision) does not exist
------------------------------------+---------------------------------------
Reporter: robe | Owner: dustymugs
Type: defect | Status: closed
Priority: blocker | Milestone: PostGIS 2.2.0
Component: build/upgrade/install | Version: trunk
Resolution: fixed | Keywords:
------------------------------------+---------------------------------------
Comment(by strk):
Alright I think the problem is that
ST_CountAGG(raste,integer,boolean,float8) was added somewhen during
development but I've created the extension _before_ its creation.
So moving from dev to devnext the AGGREGATE is documented as being already
present in the source version (2.2.0dev already) and thus is not re-
created. But it's _not_ present, so the upgrade fails to install it.
This is a general problem with dev-to-devnext when it comes to aggregates,
or generally to objects that the upgrade procedure now refrain from
installing if advertised to be already present in the version.
What we _could_ do is pretending all aggregates have to be dropped and re-
created when source and target versions are the same and they end in
"dev", or something like that. But I guess there would be still cases in
which you'd want to avoid that.
Or we could have a special "next"-like upgrade path for a full reload ?
ALTER EXTENSION postgis UPDATE TO '2.2.0devnextfull' ?
sounds like worth another ticket...
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2659#comment:20>
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.
More information about the postgis-tickets
mailing list