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

[Regina Obe]

I think we had moved them to legacy a long time ago so we don't explicitly
drop them in our scripts because we'd be dropping things people installed
with legacy.


-----Original Message-----
From: Paul Ramsey [mailto:pramsey at cleverelephant.ca] 
Sent: Tuesday, October 8, 2019 1:59 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Cc: Regina Obe <lr at pcorp.us>
Subject: Re: [postgis-devel] upgrade from postgis2.4 to 3.0 requires
dropping functions

Those probably came from a very old (pre-2.0) install and have been around
in those databases since forever. 

> 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
> 
> Thanks,
> Justin
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel