Re: Struggling with 13->14 and anyarray -> anycompatiblearray - Mailing list pgsql-admin

From Wells Oliver
Subject Re: Struggling with 13->14 and anyarray -> anycompatiblearray
Date
Msg-id CAOC+FBVs_AqBFY+0ExnHsnA9BDRwuOsHpxRL+rLuCsuxP5t5Jg@mail.gmail.com
Whole thread Raw
In response to Re: Struggling with 13->14 and anyarray -> anycompatiblearray  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Struggling with 13->14 and anyarray -> anycompatiblearray
List 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@sss.pgh.pa.us> wrote:
Wells Oliver <wells.oliver@gmail.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


--

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Struggling with 13->14 and anyarray -> anycompatiblearray
Next
From: Tom Lane
Date:
Subject: Re: Struggling with 13->14 and anyarray -> anycompatiblearray