aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2021-08-08 21:05:46 -0400
committerBruce Momjian <bruce@momjian.us>2021-08-08 21:05:46 -0400
commitd8a75b1308b133502ae3f02be485e9cd4eda9803 (patch)
treefa37e46a2ef5b1c9da5eb40efed7504ab6f2be58
parentae03a7c7391dfc59f14226b7cfd8ef9f3390e56f (diff)
downloadpostgresql-d8a75b1308b133502ae3f02be485e9cd4eda9803.tar.gz
postgresql-d8a75b1308b133502ae3f02be485e9cd4eda9803.zip
doc: mention pg_upgrade extension script
Since commit e462856a7a, pg_upgrade automatically creates a script to update extensions, so mention that instead of ALTER EXTENSION. Backpatch-through: 9.6
-rw-r--r--doc/src/sgml/ref/pgupgrade.sgml5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 0a714658050..20efdd771f5 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -309,8 +309,9 @@ make prefix=/usr/local/pgsql.new install
must be installed in the new cluster, usually via operating system
commands. Do not load the schema definitions, e.g., <command>CREATE
EXTENSION pgcrypto</command>, because these will be duplicated from
- the old cluster. (Extensions with available updates can be processed
- later using <literal>ALTER EXTENSION ... UPDATE</literal>.)
+ the old cluster. If extension updates are available,
+ <application>pg_upgrade</application> will report this and create
+ a script that can be run later to update them.
</para>
</step>