diff options
| author | Bruce Momjian | 2021-08-09 01:05:46 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2021-08-09 01:05:46 +0000 |
| commit | c3c1fe09e7c34e1abbb0d30e69b7a26abe4d1411 (patch) | |
| tree | 6d7426a289a4e3e6a9bce3115c11a46455a605b4 | |
| parent | d8650419bfbf10ae70bd24cafeadf58e107add76 (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 067d1f1f7ad..c522611746e 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -279,8 +279,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> |