Update versioning page to mention pg_upgrade, per Bruce.

git-svn-id: file:///Users/dpage/pgweb/svn-repo/trunk@2806 8f5c7a92-453e-0410-a47f-ad33c8a6b003

diff --git a/portal/template/en/support/versioning.html b/portal/template/en/support/versioning.html
index 69c830bf1f20355b8c34727a26094e986450caa8..dd649904dfa49468bd0e538cce46867574ab1d96 100644 (file)
--- a/portal/template/en/support/versioning.html
+++ b/portal/template/en/support/versioning.html
@@ -13,7 +13,7 @@ PostgreSQL major releases include new features and occur roughly once every year
 </p>
 
 <p>
-Major releases usually change the internal format of system tables and data files.  These changes are often complex, so we don't maintain backward compatibility for data files.  A dump/reload of the database is required for major upgrades.
+Major releases usually change the internal format of system tables and data files.  These changes are often complex, so we do not maintain backward compatibility of all stored data.  A dump/reload of the database or use of the <a href="http://www.postgresql.org/docs/current/static/pgupgrade.html">pg_upgrade</a> module is required for major upgrades.
 </p>
 
 <p>