[postgis-tickets] [PostGIS] #4590: Upgrading PostGIS 3.0 PG 11 to PostGIS 3.0 PG 12 errors after pg_upgrade - st_linecrossingdirection

[PostGIS]

#4590: Upgrading PostGIS 3.0 PG 11 to PostGIS 3.0 PG 12 errors after pg_upgrade -
st_linecrossingdirection
-----------------------------------+---------------------------
 Reporter:  robe                   |      Owner:  strk
     Type:  defect                 |     Status:  new
 Priority:  medium                 |  Milestone:  PostGIS 3.0.1
Component:  build/upgrade/install  |    Version:  3.0.x
 Keywords:                         |
-----------------------------------+---------------------------
 Might be something particular about this database, I'm going to try
 another.

 Here is the situation

 1) Had a PostgreSQL 11.5 database which I had upgraded to PostGIS 3.0.0
 from PostGIS 2.5.2 (or 2.5.1, can't remember)

 2) Ran pg_upgrade on the server to bring it to PostgreSQL 12, PostGIS
 3.0.0

 pg_upgrade went fine.  After upgrade


 {{{
 SELECT postgis_full_version();
 }}}

 Gives:

 {{{
 POSTGIS="3.0.0 r17983" [EXTENSION] PGSQL="110" (procs need upgrade for use
 with PostgreSQL "120") GEOS="3.8.0-CAPI-1.13.1 " PROJ="Rel. 5.2.0,
 September 15th, 2018" LIBXML="2.9.9" LIBJSON="0.12" LIBPROTOBUF="1.2.1"
 WAGYU="0.4.3 (Internal)"
 }}}


 So went to remedy the 11/12 situation by:


 {{{
 SELECT postgis_extensions_upgrade();
 }}}

 and got:

 {{{
 ERROR:  cannot change name of input parameter "line1"
 HINT:  Use DROP FUNCTION st_linecrossingdirection(geometry,geometry)
 first.
 CONTEXT:  SQL statement "ALTER EXTENSION postgis UPDATE TO "3.0.0next";"
 PL/pgSQL function postgis_extensions_upgrade() line 69 at EXECUTE
 SQL state: 42P13
 }}}


 I don't recall us renaming the args for this

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