[postgis-tickets] [PostGIS] #4639: Can't upgrade from 3.0.0alpha3 to 3.1.0dev (cannot drop function pgis_geometry_union_transfn)

[PostGIS]

#4639: Can't upgrade from 3.0.0alpha3 to 3.1.0dev (cannot drop function
pgis_geometry_union_transfn)
----------------------+---------------------------
  Reporter:  strk     |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  blocker  |  Milestone:  PostGIS 3.1.0
 Component:  postgis  |    Version:  master
Resolution:           |   Keywords:  upgrade
----------------------+---------------------------

Comment (by Algunenano):

 > Now, what do you mean by "skipping intermediates"

 I meant that you are trying to go from alpha3 -> 3.1, not alpha3 -> alpha4
 -> alpha5 -> 3.1, so you are facing issues that might have been resolved
 in the upgrade processes in between. The upgrade matrix grows
 quadratically with new releases, so supporting also upgrading from alphas
 indefinitely is madness in my book (unless we get contributors
 quadratically too).


 > A possible option could be: drop CASCADE the function _before_ the
 upgrade, and make sure AGGREGATEs are added if missing ( no matter _when_
 they were changed )

 This raises a huge red flag to me. Under no circumstances an extension
 should drop objects that weren't created by it. Doing a cascade drop could
 mean deleting views, indexes or other user created elements. That isn't an
 acceptable behaviour.

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