From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Dave Cramer <davecramer@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: pg_upgrade does not upgrade pg_stat_statements properly
Date: Thu, 29 Jul 2021 18:19:56 -0400
Message-ID: <953847.1627597196@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, davecramer@gmail.com, alvherre@alvh.no-ip.org, david.g.johnston@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: pg_upgrade does not upgrade pg_stat_statements properly
In-Reply-To: <953847.1627597196@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox