postgres.git / summary / log / commit / refs

commit    c3c1fe09e7c34e1abbb0d30e69b7a26abe4d1411
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Mon Aug 09 01:05:46 2021 +0000
First released in: 15.0, 9.6.23, 10.18, 11.13, 12.8, 13.4, 14.0

    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


 doc/src/sgml/ref/pgupgrade.sgml | 5 +++--
 1 file 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>
 


[parent: d8650419bfbf]