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

PostGIS trac at osgeo.org
Wed Feb 12 08:44:01 PST 2020


#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 strk):

 I tried installing postgis from the stable-3.0 branch. Same problem:
 {{{
 psql:postgis/postgis_upgrade.sql:7634: ERROR:  cannot drop function
 pgis_geometry_union_transfn(internal,geometry) because other objects
 depend on it
 DETAIL:  function st_union(geometry) depends on function
 pgis_geometry_union_transfn(internal,geometry)
 HINT:  Use DROP ... CASCADE to drop the dependent objects too.
 }}}

 Upgrade info:
 {{{
 strk=# select * from _postgis_upgrade_info;
  scripts_upgraded |   scripts_installed   | version_to_num |
 version_from_num | version_from_isdev
 ------------------+-----------------------+----------------+------------------+--------------------
  3.0              | 3.0.0alpha3dev r17535 |                |
 300 | t
 (1 row)
 }}}

 The upgrade procedure will ONLY drop/re-create the aggregate IFF coming
 from 2.5 (because the comment says that the aggregate was ONLY changed in
 2.5, not in 3.0).

 If we dont support upgrades from alpha we should really not ship alphas at
 all. How can people possibly test if upgrading to an alpha can put them in
 a situation to be impossible to upgrade ?

 Really, we need to fix this. If the AGGREGATE signature changed at some
 point, we need to encode that it changed.

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