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
commitbe500101705c65104af41eaad5e36906b52f44b2 (patch)
treea32775b1e4dcfa0c7c5ecc90958f9e5a1e8fac52
parent08ef2ce204573688a3216de39dd7fc2744a563a6 (diff)
downloadpostgresql-be500101705c65104af41eaad5e36906b52f44b2.tar.gz
postgresql-be500101705c65104af41eaad5e36906b52f44b2.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 2c65d48cd27..0b2d76bd386 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -308,8 +308,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>