summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian2017-02-25 17:59:23 +0000
committerBruce Momjian2017-02-25 17:59:23 +0000
commitddcfeba95e2cdb90b1f37ac5cae97124373fa076 (patch)
tree8af36079045f082f2b5e3078df350e5ea023f8cc /doc/src
parent98755681a2bde0d4970836b517c7f2ca8c996cfc (diff)
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
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/pgupgrade.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index ae0346a22d4..20e27f52d94 100644
--- 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. <filename>pgcrypto.so</filename>,
whether they are from <filename>contrib</filename>
or some other source. Do not install the schema definitions, e.g.
- <filename>pgcrypto.sql</>, because these will be upgraded from the old cluster.
+ <command>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.
</para>