Re: pg_upgrade (12->14) fails on aggregate
x4mmm@yandex-team.ru
From: Andrey Borodin <x4mmm@yandex-team.ru>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
Robert Haas <robertmhaas@gmail.com>,
"David G. Johnston" <david.g.johnston@gmail.com>,
Petr Vejsada <pve@paymorrow.com>,
pgsql-hackers@lists.postgresql.org
Date: 2022-06-29T18:43:00Z
Lists: pgsql-bugs, pgsql-hackers
> On 29 Jun 2022, at 23:07, Justin Pryzby <pryzby@telsasoft.com> wrote: > > On Wed, Jun 29, 2022 at 10:58:44PM +0500, Andrey Borodin wrote: >>> On 28 Jun 2022, at 04:30, Justin Pryzby <pryzby@telsasoft.com> wrote: >>> >>> Nope, it's as I said: this would break pg_upgrade from older versions. >> >> As far as I understand 9.5 is not supported. Probably, it makes sense to keep pg_upgrade running against 9.5 clusters, but I'm not sure if we do this routinely. > > As of last year, there's a reasonably clear policy for support of old versions: > > https://www.postgresql.org/docs/devel/pgupgrade.html > |pg_upgrade supports upgrades from 9.2.X and later to the current major release of PostgreSQL, including snapshot and beta releases. This makes sense, thank you for clarification. The patch is marked WiP, what is in progress as of now? Best regards, Andrey Borodin.
Commits
-
Tighten pg_upgrade's new check for non-upgradable anyarray usages.
- c7e21e966464 15.0 landed
- 08385ed26196 16.0 landed
- 9783413cbff9 14.5 landed
-
Fix pg_upgrade to detect non-upgradable anyarray usages.
- c069f427855a 15.0 landed
- 175e60a5e35e 14.5 landed
- 09878cdd489f 16.0 landed
-
Remove pg_upgrade support for upgrading from pre-9.2 servers.
- e469f0aaf3c5 15.0 cited