[postgis-devel] Postgis 3.1 minimum requirements update

[Regina Obe]

You can always install legacy.sql ontop of extensions.  For the cases I need it (which is rare I do) that.

I think DBaaS systems I forget which one - perhaps it was heroku even packaged the legacy.sql as an extension to get around the power user issue.

I've been thinking we probably should do the same - just bite the bullet and have legacy.sql be packaged as an extension.

It is kind of annoying that I have to give extra instructions about how to upgrade it.

If it were an extension - then upgrading it would be part of the 

SELECT postgis_extensions_upgrade();

Command



-----Original Message-----
From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Justin Pryzby
Sent: Monday, November 11, 2019 3:17 PM
To: postgis-devel at lists.osgeo.org
Subject: Re: [postgis-devel] Postgis 3.1 minimum requirements update

On Mon, Nov 11, 2019 at 07:54:57PM +0100, Christoph Berg wrote:
> Most of the support requests around PostGIS we get at the company 
> revolve around users having trouble upgrading non-extension 
> installations. Why is that still a thing?

Is it because of legacy.sql ?
I've (finally) added that to our TODO list here.

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