[postgis-devel] Upgrade PostGIS from 2.5.4 to 3.1.2

[Nikhil Shetty]

Hi Team,

I have followed the steps mentioned by Regina. Just to add a few more
details. After database  upgrade you may see below message:

upgrade_testdb_dev=# SELECT postgis_full_version();


                          postgis_full_version




----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

---------------

 POSTGIS="3.1.2 cbe925d" [EXTENSION] PGSQL="110" (procs need upgrade for
use with PostgreSQL "130") GEOS="3.9.1-CAPI-1.14.2" PROJ="7.2.1" GDAL="GDAL
3.2.3, released 2021/04/27" LIBXML="2.9.1" LIBJSON="0.11" T

OPOLOGY RASTER

(1 row)



Run the upgrade command again to resolve this on Pg13

upgrade_testdb_dev=# SELECT postgis_extensions_upgrade();

NOTICE:  Updating extension postgis 3.1.2

NOTICE:  Extension postgis_sfcgal is not available or not packagable for
some reason

NOTICE:  Extension postgis_tiger_geocoder is not available or not
packagable for some reason

                    postgis_extensions_upgrade

-------------------------------------------------------------------

 Upgrade completed, run SELECT postgis_full_version(); for details


upgrade_testdb_dev=# SELECT postgis_full_version();


     postgis_full_version


----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 POSTGIS="3.1.2 cbe925d" [EXTENSION] PGSQL="130" GEOS="3.9.1-CAPI-1.14.2"
PROJ="7.2.1" GDAL="GDAL 3.2.3, released 2021/04/27" LIBXML="2.9.1"
LIBJSON="0.11" TOPOLOGY RASTER

(1 row)


I have seen one blog which says that a direct upgrade from 2.4.6 to 3.1.2
has many dependencies on raster functions and we should upgrade to 3.1.1
and then to 3.1.2. They have mentioned postgis 2.4.6 but Is it valid in my
case also? I am upgrading postgis from 2.5.4 to 3.1.2.

Blog -
https://www.enterprisedb.com/docs/postgis/3.1.2/03_upgrading_postgis/#example-2

On Thu, Jan 27, 2022 at 3:26 PM Sandro Santilli <strk at kbt.io> wrote:

> On Wed, Jan 26, 2022 at 04:04:51PM -0500, Regina Obe wrote:
>
> > In addition, having the lib not change, means you are not fully upgraded
> > until you run the
> >
> > SELECT postgis_extensions_upgrade()  or ALTER EXTENSION ..
>
> This is STILL the case. You are NOT fully upgraded until you run
>
>   SELECT postgis_extensions_upgrade()
>
> Let's make it very clear for users that upgrading files on the
> operating system level is NOT enough for upgrading postgis databases.
>
> > Which means for basic use, you can easily test with just the new lib, and
> > back out of an upgrade by uninstalling the new version and reinstalling
> the
> > old version.
>
> You would really only be testing specific kind of changes (not any new
> or changed signature, not any script-only speedup or refactoring or bugfix)
> and could also incur in crashes due to scripts being incompatible with
> underlying library. Let's remember we currently have NO automated test
> coverage of these kind of upgrades.
>
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20220128/8aba1ed4/attachment-0001.html>