From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: Dave Cramer <davecramer@gmail.com>,
        Alvaro Herrera <alvherre@alvh.no-ip.org>,
        "David G. Johnston" <david.g.johnston@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: pg_upgrade does not upgrade pg_stat_statements properly
In-reply-to: <20210729221103.GV9600@momjian.us>
References: <20210729163448.GP9600@momjian.us>
 <202107291743.pqlj3s2uilfu@alvherre.pgsql> <20210729190645.GS9600@momjian.us>
 <CADK3HHLZP=3HYNY_qsVBDQt83F7QpY_WrqXGN=KkQZCxraOyLA@mail.gmail.com>
 <915981.1627592484@sss.pgh.pa.us> <20210729221103.GV9600@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Thu, 29 Jul 2021 18:11:03 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <953846.1627597196.1@sss.pgh.pa.us>
Date: Thu, 29 Jul 2021 18:19:56 -0400
Message-ID: <953847.1627597196@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/953847.1627597196%40sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> I think we need to first give clear instructions on how to find out if
> an extension update is available, and then how to update it.  I am
> thinking we should supply a query which reports all extensions that can
> be upgraded, at least for contrib.

I suggested awhile ago that pg_upgrade should look into
pg_available_extensions in the new cluster, and prepare
a script with ALTER EXTENSION UPDATE commands for
anything that's installed but is not the (new cluster's)
default version.

			regards, tom lane