From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: array_cat anycompatible change is breaking xversion upgrade tests (v14 release notes) |
Date: | 2021-06-12 01:19:48 |
Message-ID: | 20210612011948.GR16435@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 11, 2021 at 09:12:55PM -0400, Bruce Momjian wrote:
> OK, I used some of your ideas and tried for something more general;
> patch attached.
This is good.
But I wonder if "dropped before upgrading" is too specific to pg_upgrade?
Dropping the aggregate before starting a backup to be restored into a new
version seems like a bad way to do it. More likely, I would restore whatever
backup I had, get errors, and then eventually recreate the aggregates.
> + <para>
> + User-defined objects that reference some built-in array functions
> + along with their argument types must be recreated (Tom Lane)
> + </para>
> +
> + <para>
> + Specifically, <link
> + linkend="functions-array"><function>array_append()</function></link>,
...
> + used to take <type>anyarray</type> arguments but now take
> + <type>anycompatiblearray</type>. Therefore, user-defined objects
> + that reference the old array function signature must be dropped
> + before upgrading and recreated once the upgrade completes.
> + </para>
> + </listitem>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2021-06-12 01:40:07 | Re: array_cat anycompatible change is breaking xversion upgrade tests (v14 release notes) |
Previous Message | Tom Lane | 2021-06-12 01:17:46 | Re: array_cat anycompatible change is breaking xversion upgrade tests (v14 release notes) |