note in docs about soft upgrade that legacy.sql must be rerun for each minor.

Closes #2960 for PostGIS 2.4.4

git-svn-id: http://svn.osgeo.org/postgis/branches/2.4@16495 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/doc/installation.xml b/doc/installation.xml
index b6e0100cd11f1b68a4e8c104fc580f1bb6152d8f..e57637e9b4997f4b5c69d7254aea4ae8e9457797 100644 (file)
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -1401,6 +1401,9 @@ All 2 tests passed.
        <para>If you plan to restore an old backup from prior versions in this new db, run:</para>
        <para><command>psql -d [yourdatabase] -f legacy.sql</command></para>
 
+       <note><para>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.3.7 to 2.4.4, then you need to reinstall the legacy.sql packaged with 2.4.4.  This is because some of the functions make reference to the library
+       and the library is named with the minor in it.</para></note>
        <para>You can later run <filename>uninstall_legacy.sql</filename> to get rid of the deprecated functions after you are done with restoring and cleanup.</para>
   </sect1>