diff options
author | Bruce Momjian | 2017-02-25 17:59:23 +0000 |
---|---|---|
committer | Bruce Momjian | 2017-02-25 17:59:23 +0000 |
commit | 5639ceddcb7f3efa8751b2ba6e50cc1d27cc2a45 (patch) | |
tree | 8f64dd09e35da904dcb3884f0f1deaea534c1312 | |
parent | c5658a0764d5ac5ea8c2c11d27c62d5472234227 (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
-rw-r--r-- | doc/src/sgml/ref/pgupgrade.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index ad28526296..49aaf513f5 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> |