aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2017-02-25 12:59:23 -0500
committerBruce Momjian <bruce@momjian.us>2017-02-25 12:59:23 -0500
commitf97f4fc028ccc284683ba400a51d59e534901336 (patch)
treea7a52a332c47e3173c10aa5c4f0e60a0b4a41b09
parentcb8ef68b93312e3977f3e60676ded9a553c14064 (diff)
downloadpostgresql-f97f4fc028ccc284683ba400a51d59e534901336.tar.gz
postgresql-f97f4fc028ccc284683ba400a51d59e534901336.zip
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
-rw-r--r--doc/src/sgml/ref/pgupgrade.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 96851933cc5..bbb606d1caa 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -273,7 +273,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>