[postgis-tickets] [PostGIS] #2766: Aggregates created in same minor are missed

[PostGIS]

#2766: Aggregates created in same minor are missed
-----------------------------------+----------------------------------------
 Reporter:  robe                   |       Owner:  strk         
     Type:  defect                 |      Status:  new          
 Priority:  medium                 |   Milestone:  PostGIS 2.2.0
Component:  build/upgrade/install  |     Version:  2.1.x        
 Keywords:                         |  
-----------------------------------+----------------------------------------
 We have an issue that if an aggregate is changed or created in same minor,
 it will not be recreated or created.

 E.g. If you create an aggregate in 2.2.0 and upgrade to 2.2.0devnext you
 may not get the new aggregate.

 While this is an issue mostly for interim dev upgrades, I think it may be
 an issue too for general micro upgrades -- e.g. 2.1.0 to  2.1.3.

 Although it is our policy to not change the APIs between micros (and to
 avoid introducing new functions except where necessary), technically since
 changing the underlying functions used to support an aggregate don't
 change the api of aggregate this should be allowed.

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