Horton

Re: pg_upgrade (12->14) fails on aggregate

David G. Johnston <david.g.johnston@gmail.com>

View thread View on postgr.es
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Petr Vejsada <pve@paymorrow.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-05-04T14:34:15Z
Lists: pgsql-bugs, pgsql-hackers 
On Wed, May 4, 2022 at 7:29 AM Petr Vejsada <pve@paymorrow.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.

Commits

  1. Tighten pg_upgrade's new check for non-upgradable anyarray usages.

  2. Fix pg_upgrade to detect non-upgradable anyarray usages.

  3. Remove pg_upgrade support for upgrading from pre-9.2 servers.