From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Struggling with 13->14 and anyarray -> anycompatiblearray |
Date: | 2022-11-04 20:51:59 |
Message-ID: | CAOC+FBVs_AqBFY+0ExnHsnA9BDRwuOsHpxRL+rLuCsuxP5t5Jg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks. This seems to return aggregates where array_append is used with
anyarray, but I now see aggregates where e.g. array_cat is used with
anyarray. Is there some way to generally query aggregates where any array
function might be looking for anyarray and need to be dropped/re-created
with anycompatiblearray?
On Fri, Nov 4, 2022 at 12:12 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Wells Oliver <wells(dot)oliver(at)gmail(dot)com> writes:
> > I've inherited a DB with a lot of legacy functions and aggregates that
> have
> > an SFUNC of array_append and an STYPE of anyarray.
> > Is there some way I can query for these aggregates/functions and see how
> > many I need to drop and have available to replace after a
> > successful upgrade?
>
> Something like
>
> select aggfnoid::regprocedure from pg_aggregate where aggtransfn =
> 'array_append'::regproc;
>
> regards, tom lane
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-11-04 21:31:29 | Re: Struggling with 13->14 and anyarray -> anycompatiblearray |
Previous Message | Tom Lane | 2022-11-04 19:12:49 | Re: Struggling with 13->14 and anyarray -> anycompatiblearray |