Well, this speaks to not having micro version numbers in the extension versioning, for sure. Also, potentially for having a global source version, an idea that we’d have to add to the PgSQL extension system, so a script like postgis—ANY—2.3.sql could take a best-effort run at upgrading any prior installed version. It can perhaps be fixed by copying postgis—2.3.0--2.3.1.sql (or, really, any of the extension upgrade scripts) to postgis—2.1.4–2.3.1.sql P.
> On Apr 3, 2019, at 10:34 AM, Paolo Cavallini <cavall...@faunalia.it> wrote: > > > > On 03/04/19 19:04, Sandro Santilli wrote: >> Can you show the ALTER EXTENSION command you're issuing and the >> error you're getting ? Also please show the output of >> >> SELECT postgis_full_version(); > > I tried both > ALTER EXTENSION postgis UPDATE; > with something like > the 2.1.4 version is already installed > and > ALTER EXTENSION postgis > UPDATE TO "2.3.1" > with > ERRORE: l'estensione "postgis" non ha un percorso di aggiornamento > dalla versione "2.1.4" alla versione "2.3.1" > > unfortunately the VPN just went down, and I don't have currently access > to the machine. > Thanks a lot. > -- > Paolo Cavallini - www.faunalia.eu > QGIS.ORG Chair: > http://planet.qgis.org/planet/user/28/tag/qgis%20board/ > _______________________________________________ > postgis-users mailing list > postgis-users@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/postgis-users _______________________________________________ postgis-users mailing list postgis-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/postgis-users