[postgis-tickets] [PostGIS] #4483: Can't upgrade from PostGIS 3.0.0alpha3 to 3.0.0alpha4 or 3.0.0alpha5dev (ST_AsGeoJSON)

[PostGIS]

#4483: Can't upgrade from PostGIS 3.0.0alpha3 to 3.0.0alpha4 or 3.0.0alpha5dev
(ST_AsGeoJSON)
----------------------+---------------------------
  Reporter:  robe     |      Owner:  pramsey
      Type:  defect   |     Status:  reopened
  Priority:  blocker  |  Milestone:  PostGIS 3.0.1
 Component:  postgis  |    Version:  master
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by Algunenano):

 > If the above is correct then the commit in r17879 should just be
 reverted as there's never been a default-less version taking a record as
 first argument ?

 Yes, I think so too.

 > If the above is correct then the commit in r17879 should just be
 reverted as there's never been a default-less version taking a record as
 first argument ?

 Also yes, we should have a drop in place for all signatures that have
 disappeared.


 > Also I noticed we have a couple of the removed functions in legacy.sql,
 does it make sense to have things both in postgis_after/before_upgrade and
 in legacy.sql ?

 It seems like the original intention of legacy.sql was to facilitate the
 upgrade to Postgis 2, and I'm not sure if we keep it around for anything
 else. If the only use for the file is for 1.x -> 2.x upgrade, I think it's
 time to drop it and ask people to update to intermediate releases (1.x ->
 2.x/3.0, 2.x -> 3.1).

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