[postgis-users] Moving from Postgis 2.5.5 to Postgis 3.0

Regina Obe lr at pcorp.us
Wed Sep 30 06:31:58 PDT 2020

You don't need to run the perl script if you installed using extensions.
The perl script is only needed if you used what I called "Old Fashioned
using scripts".


That said your steps are fine.  You don't need to do not need to go to 2.5.5
in old before going to 3.0 in new.



One other consideration: 


If you are using PostGIS raster, you will need to create your new database
first and then do 



CREATE EXTENSION postgis; SCHEMA <same schema as you have installed your

CREATE EXTENSION postgis_raster SCHEMA <same schema as you have installed
your 9.6>;


Otherwise your raster tables will not load.


I'll work on clarifying the instructions in the docs, but if you can think
of a better way of describing it, feel free to provide a patch to the docs.


Hope that helps,





From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] On Behalf
Of Reismann, Martin
Sent: Wednesday, September 30, 2020 8:56 AM
To: postgis-users at lists.osgeo.org
Subject: [postgis-users] Moving from Postgis 2.5.5 to Postgis 3.0




I am planning to move from Postgis 2.5.5 (on PostgreSQL 9.6) to Postgis 3.0
(on PostgreSQL 13).


I refer to


Can I proceed as follows (HARD UPGRADE) ?

- pg_dump database(s) in old system

- install Postgis 3.0 packages on operating system level

- initialization of new database, start the new server, import of users and
groups ...

- restore database(s) in new system (using the perl script given in the link

- ALTER EXTENSION postgis UPDATE TO "3.0.2"; # in new system





Is it still necessary to do an in-place SOFT UPGRADE (ALTER EXTENSION
postgis UPDATE ...) of Postgis 2.5.5  to 3.0 BEFORE starting the procedure
above ?



There is an older docment which mentions this:



"Install the new version of PostgreSQL and the same version of PostGIS you
are using in your old database. You need to match the PostGIS version so
that the dump file function definitions reference an expected version of the
PostGIS library."



Martin Reismann











-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20200930/b6ee73b5/attachment.html>

More information about the postgis-users mailing list