From a99f879b67a03ffea04de6ad289664e9961cde98 Mon Sep 17 00:00:00 2001 From: Regina Obe Date: Sat, 24 Mar 2018 02:12:46 +0000 Subject: [PATCH] note in docs about soft upgrade that legacy.sql must be rerun for each minor. References #2960 for PostGIS 2.5.0 (trunk) git-svn-id: http://svn.osgeo.org/postgis/trunk@16494 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/installation.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/installation.xml b/doc/installation.xml index b6e0100cd..d7a112fd5 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -1400,7 +1400,9 @@ All 2 tests passed. If you plan to restore an old backup from prior versions in this new db, run: psql -d [yourdatabase] -f legacy.sql - + If you need legacy functions, you'll need to reinstall the legacy.sql script whenever you upgrade the minor version of PostGIS. + E.g. if you upgraded from 2.4.3 to 2.5.0, then you need to reinstall the legacy.sql packaged with 2.5.0. This is because some of the functions make reference to the library + and the library is named with the minor in it. You can later run uninstall_legacy.sql to get rid of the deprecated functions after you are done with restoring and cleanup. -- 2.40.0