[postgis-devel] upgrade from postgis2.4 to 3.0 requires dropping functions

[Regina Obe]

What error did you get if you don't drop them.

Usually the issue with aggregates is when you have functions or views reliant on them, but then you'd need to drop those as well.

I also though extent(geometry) is a legacy function.  Did you have legacy script installed as well?

When you say postgis_upgrade.sql, are you running that?  or using

CREATE EXTENSION postgis UPDATE;

-----Original Message-----
From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Justin Pryzby
Sent: Friday, September 27, 2019 10:25 PM
To: postgis-devel at lists.osgeo.org
Subject: [postgis-devel] upgrade from postgis2.4 to 3.0 requires dropping functions

While testing upgrades, I found that I had to first manually drop these before running v3.0's postgis_upgrade.sql.

DROP FUNCTION _st_linecrossingdirection(geometry,geometry);
DROP FUNCTION _st_orderingequals(geometry,geometry);
DROP FUNCTION st_linecrossingdirection(geometry,geometry);
DROP AGGREGATE st_extent3d(geometry);
DROP AGGREGATE extent(geometry);

I'm using:

postgis24_11-2.4.8-5.rhel7.x86_64
postgis30_11-3.0.0alpha4-6.rhel7.x86_64

Justin
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-devel