From ff18b8d1b169b2bf47daab7d92c5376bc19c0748 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 8 Aug 2021 21:05:46 -0400
Subject: [PATCH] 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 cb047ac4f3..7e3158685d 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>