From 19a49d02a41f50d8c19ad20972395b464edc68dc Mon Sep 17 00:00:00 2001 From: Sandro Santilli Date: Wed, 31 Oct 2012 09:46:22 +0000 Subject: [PATCH] Add instruction for upgrading between SVN revisions using extensions git-svn-id: http://svn.osgeo.org/postgis/trunk@10606 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/installation.xml | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/doc/installation.xml b/doc/installation.xml index e365dfc00..036523114 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -1178,10 +1178,19 @@ pretty_address ALTER EXTENSION postgis_topology UPDATE TO "&last_release_version;"; If you get an error notice something like: No migration path defined for ... to &last_release_version; - Then you'll need to backup your database, create a fresh one as described in and then restore your backup ontop of this new database. - You might get a message that postgis extension already installed which you can safely ignore. + Then you'll need to backup your database, create a fresh one as described in and then restore your backup ontop of this new database. + If you get a notice message like: + Version "&last_release_version;" of extension "postgis" is already installed + +Then everything is already up to date and you can safely ignore it. UNLESS +you're attempting to upgrade from an SVN version to the next (which +doesn't get a new version number); in that case you can append "next" to the version +string, and next time you'll need to drop the "next" suffix again: + + ALTER EXTENSION postgis UPDATE TO "&last_release_version;next"; +ALTER EXTENSION postgis_topology UPDATE TO "&last_release_version;next"; If you installed PostGIS originally without a version specified, you can often skip the reinstallation of postgis extension before restoring since the backup just has CREATE EXTENSION postgis and thus - picks up the newest latest version during restore. . + picks up the newest latest version during restore. -- 2.40.0