diff options
| author | Bruce Momjian | 2021-08-09 01:05:46 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2021-08-09 01:05:46 +0000 |
| commit | 9268fc34526427a48bc27b5ac4727c7fb4cddf7a (patch) | |
| tree | 3d270d46d06faa17c768d263b1355c4364b418b6 | |
| parent | c905e64d42fe0725ab7fe84b70a41b4c381aee07 (diff) | |
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.sgml | 5 |
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> |