From: Sandro Santilli <strk@keybit.net>
Date: Wed, 29 Feb 2012 10:39:42 +0000 (+0000)
Subject: Mention rtpostgis_upgrade* and topology_upgrade* in manual (#1611)
X-Git-Tag: 2.0.0beta1~11
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=eef716e2203c36ac01dc1d14c82b9f457494a55a;p=postgis

Mention rtpostgis_upgrade* and topology_upgrade* in manual (#1611)

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

diff --git a/doc/installation.xml b/doc/installation.xml
index 814deeff9..75c17398c 100644
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -1080,12 +1080,30 @@ pretty_address
 
 	  <programlisting>psql -f postgis_upgrade_20_minor.sql -d your_spatial_database</programlisting>
 
+	  <para>
+		The same procedure applies to raster and
+		topology extensions, with upgrade files named
+		<filename>rtpostgis_upgrade*.sql</filename> and
+		<filename>topology_upgrade*.sql</filename> respectively.
+		If you need them:
+	  </para>
+
+	  <programlisting>psql -f rtpostgis_upgrade_20_minor.sql -d your_spatial_database</programlisting>
+	  <programlisting>psql -f topology_upgrade_20_minor.sql -d your_spatial_database</programlisting>
+
 	  <note>
 		<para>
 		  If you can't find the <filename>postgis_upgrade*.sql</filename> specific for upgrading your version you are using a version too early for
 		  a soft upgrade and need to do a HARD UPGRADE.
 		</para>
 	  </note>
+
+	  <para>
+		The <xref linkend="PostGIS_Full_Version" /> function
+		should inform you about the need to run this kind of
+		upgrade using a "procs need upgrade" message.
+	  </para>
+
 	</sect2>
 
 	<sect2 id="hard_upgrade">