]> granicus.if.org Git - postgis/commitdiff
Update the upgrade process description to match new scripts.
authorPaul Ramsey <pramsey@cleverelephant.ca>
Mon, 30 Nov 2009 19:12:35 +0000 (19:12 +0000)
committerPaul Ramsey <pramsey@cleverelephant.ca>
Mon, 30 Nov 2009 19:12:35 +0000 (19:12 +0000)
git-svn-id: http://svn.osgeo.org/postgis/trunk@4941 b70326c6-7e19-0410-871a-916f4a2858ee

README.postgis

index b7fdf6700545492d8f40b9bc6097755233d92492..45ee6b6ff7e101dbfef4e43bacc4537fdac6e74a 100644 (file)
@@ -168,14 +168,21 @@ releases, and an HARD UPGRADE procedure for major releases.
 
 --- SOFT UPGRADE ---
 
-Soft upgrade consists of sourcing the postgis_upgrade.sql
+
+Soft upgrade consists of sourcing the postgis_upgrade_*.sql
 script in your spatial database:
 
-  psql -f postgis_upgrade.sql -d your_spatial_database
+ * postgis_upgrade_13_to_15.sql, upgrade a 1.3.x database
+   to 1.5
+ * postgis_upgrade_15_to_15.sql, upgrade a 1.4.x database 
+   to 1.5
+ * postgis_upgrade_16_minor.sql, upgrade a 1.5.x database
+   to the latest minor release
 
 If a soft upgrade is not possible the script will abort and 
-you will be warned about HARD UPGRADE being required,
-so do not hesitate to try a soft upgrade first.
+no harm will be done. You can then move on to the 
+HARD UPGRADE process. Always try a soft upgrade first, they 
+are much simpler.
 
 --- HARD UPGRADE ---