| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Petr Vejsada <pve(at)paymorrow(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_upgrade (12->14) fails on aggregate |
| Date: | 2022-06-29 18:07:14 |
| Message-ID: | 20220629180714.GN28130@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Jun 29, 2022 at 10:58:44PM +0500, Andrey Borodin wrote:
> > On 28 Jun 2022, at 04:30, Justin Pryzby <pryzby(at)telsasoft(dot)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.
See: e469f0aaf3c586c8390bd65923f97d4b1683cd9f
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2022-06-29 18:43:00 | Re: pg_upgrade (12->14) fails on aggregate |
| Previous Message | Andrey Borodin | 2022-06-29 17:58:44 | Re: pg_upgrade (12->14) fails on aggregate |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2022-06-29 18:43:00 | Re: pg_upgrade (12->14) fails on aggregate |
| Previous Message | Andrey Borodin | 2022-06-29 17:58:44 | Re: pg_upgrade (12->14) fails on aggregate |