pg_upgrade docs: clarify instructions on standby extensions

Previously the pg_upgrade standby upgrade instructions said not to
execute pgcrypto.sql, but it should have referenced the extension
command "CREATE EXTENSION pgcrypto".  This patch makes that doc change.

Reported-by: a private bug report
Backpatch-through: 9.4, where standby instructions were added

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index ae0346a22d4ce635c7a32feb69c339a0fc1e00ec..20e27f52d94c6a0fa617b5c10dacb564333e3af9 100644 (file)
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -280,7 +280,8 @@ make prefix=/usr/local/pgsql.new install
      into the new cluster, e.g. pgcrypto.so,
      whether they are from contrib
      or some other source. Do not install the schema definitions, e.g.
-     pgcrypto.sql, because these will be upgraded from the old cluster.
+     CREATE EXTENSION pgcrypto, because these will be upgraded
+     from the old cluster.
      Also, any custom full text search files (dictionary, synonym,
      thesaurus, stop words) must also be copied to the new cluster.