[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
Resolution:                         |   Keywords:
------------------------------------+---------------------------

Comment (by strk):

 Note that the only way to change an aggregate definition is to drop it and
 re-create it, and this is not possible IFF the aggregate is used by a user
 view, making a soft upgrade impossible. For this very reason it should be
 highly discouraged to change an aggregate definition in a micro (as you're
 talking about _micro_, not _minor_) upgrades.

 That said, the whole upgrade machinery only uses two version (major and
 minor) to determine whether something was added so it is hard-coded that
 nothing changes in a micro. Do we really want to change that ? Do you have
 a real example of when such change happened in a micro ?

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/2766#comment:2>
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.