| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Petr Vejsada <pve(at)paymorrow(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade (12->14) fails on aggregate |
| Date: | 2022-05-04 14:34:15 |
| Message-ID: | CAKFQuwbUUwkO0ffRY4+z4Hs9-jRjAUwGHZrDKyHhRudWVhtgkw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, May 4, 2022 at 7:29 AM Petr Vejsada <pve(at)paymorrow(dot)com> wrote:
> We solved it (in our case) dropping the aggregate before upgrade and
> re-create
> in using new syntax in V14:
>
> but pg_upgrade shouldn't fail on this.
>
> I hope it can help to improve pg_upgrade process.
>
>
The release notes say explicitly that one needs to drop and recreate the
affected functions. Thus, we know about the issue and to date our best
solution is to have the user do exactly what you did (i.e., it is not
something pg_upgrade is going to do for you). If you have an alternative
solution to suggest that would help.
https://www.postgresql.org/docs/current/release-14.html : the first
compatibility note
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2022-05-04 19:01:27 | Re: Query generates infinite loop |
| Previous Message | Petr Vejsada | 2022-05-04 13:05:32 | pg_upgrade (12->14) fails on aggregate |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2022-05-04 14:39:45 | Re: SQL/JSON: FOR ORDINALITY bug |
| Previous Message | Jakub Wartak | 2022-05-04 14:08:25 | RE: strange slow query - lost lot of time somewhere |