[postgis-devel] Pg13 upgrade issues?

[Regina Obe]

Because the postgis_extensions_upgrade() takes no arguments.

 

It reads the latest version from postgis.config  postgis-raster.config.

 

I suspect you installed 3.1 first and then 2.5 after.  So 2.5 is considered the default.

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Thursday, September 10, 2020 12:31 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] Pg13 upgrade issues?

 

 

Further to this, since it's possible to install 2.5 on Pg13, I thought I'd check to see what a naive upgrade would look like, and it's this:

 

postgis25=# alter extension postgis update to '3.1.0dev';
WARNING:  unpackaging raster
WARNING:  PostGIS Raster functionality has been unpackaged
HINT:  type `SELECT postgis_extensions_upgrade();` to finish the upgrade. After upgrading, if you want to drop raster, run: DROP EXTENSION postgis_raster;
ALTER EXTENSION
postgis25=# SELECT postgis_extensions_upgrade();
NOTICE:  Updating extension postgis from 3.1.0dev to 2.5.5dev
ERROR:  extension "postgis" has no update path from version "3.1.0dev" to version "2.5.5dev"
CONTEXT:  SQL statement "ALTER EXTENSION postgis UPDATE TO "2.5.5dev";"
PL/pgSQL function postgis_extensions_upgrade() line 68 at EXECUTE

 

Why the order of upgrade version gets flipped around in postgis_extensions_upgrade() is a bit of a mystery to me.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20200910/1b655b8d/attachment.html>