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
commitff18b8d1b169b2bf47daab7d92c5376bc19c0748 (patch)
tree4960e9236f4809794826678c37dab3d46b4ee5f2
parent410c5a08df4381917cd6da7d94609644e10ca322 (diff)
downloadpostgresql-ff18b8d1b169b2bf47daab7d92c5376bc19c0748.tar.gz
postgresql-ff18b8d1b169b2bf47daab7d92c5376bc19c0748.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 cb047ac4f3f..7e3158685d1 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>