[postgis-tickets] [PostGIS] #3821: Don't drop st_union when updating postgis extension to 2.4

[PostGIS]

#3821: Don't drop st_union when updating postgis extension to 2.4
--------------------------+---------------------------
  Reporter:  nextstopsun  |      Owner:  robe
      Type:  defect       |     Status:  new
  Priority:  medium       |  Milestone:  PostGIS 2.5.0
 Component:  postgis      |    Version:  2.3.x
Resolution:               |   Keywords:
--------------------------+---------------------------

Comment (by nextstopsun):

 I'm on 9.6.
 I've got an early postgis 2.4.0dev, but I need some recent ST_AsMVTGeom
 fixes, so now I face this DROP AGGREGATE problem.
 I understand it's mostly an upstream problem not being able to set
 aggregate properties.
 So if I'll accept the pain of killing my DB and recreating almost from
 scratch, should I get more of this when doing further extension updates? I
 can think of avoiding it by wrapping postgis functions in my own to
 decouple from view definitions, but it seems ugly to even think of this
 kind of workaround.

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