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

[Justin Pryzby]

On Tue, Oct 08, 2019 at 10:58:57AM -0700, Paul Ramsey wrote:
> Those probably came from a very old (pre-2.0) install and have been around in those databases since forever. 

Very possibly, but I wanted to report continuing to need to do this in order to
get legacy.sql to run to completion, including in 3.0 (final).

Ah, data point: I'm using ON_ERROR_STOP=1:
|psql -v ON_ERROR_STOP=1 ts -f /usr/pgsql-11/share/contrib/postgis-3.0/legacy.sql

DROP AGGREGATE st_extent3d(geometry), extent(geometry);
DROP AGGREGATE extent3d(geometry); -- repeated in arithmetic progression ...
DROP AGGREGATE extent(geometry);
DROP AGGREGATE makeline(geometry);
DROP AGGREGATE extent(geometry);
DROP AGGREGATE extent3d(geometry);
DROP AGGREGATE makeline(geometry);
DROP AGGREGATE memcollect ;
DROP AGGREGATE memcollect (geometry) ;
DROP AGGREGATE extent(geometry);
DROP AGGREGATE extent3d(geometry);
DROP AGGREGATE makeline(geometry);
DROP AGGREGATE memcollect (geometry) ;

On Oct 8, 2019, at 10:55 AM, Justin Pryzby <pryzby at telsasoft.com> wrote:
> While upgrading another (set of) DBs, I had to additionally drop these:
> 
> DROP AGGREGATE extent3d ( geometry) ;
> DROP AGGREGATE extent (geometry) ;
> DROP AGGREGATE makeline(geometry);
> DROP AGGREGATE memcollect ( geometry) ;
> 
> I currently have installed:
> postgis30_12-3.0.0alpha4-6.rhel7.1.x86_64

-- 
Justin Pryzby
System Administrator
Telsasoft
+1-952-707-8581