From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Struggling with 13->14 and anyarray -> anycompatiblearray
Date: Fri, 04 Nov 2022 17:31:29 -0400
Message-ID: <2491000.1667597489@sss.pgh.pa.us> (raw)
In-Reply-To: <CAOC+FBVs_AqBFY+0ExnHsnA9BDRwuOsHpxRL+rLuCsuxP5t5Jg@mail.gmail.com>
References: <CAOC+FBWmZ0Btu5bqkLy5pp82JVtE6z677uCjkzRnkJMZzY6mtQ@mail.gmail.com>
<2475533.1667589169@sss.pgh.pa.us>
<CAOC+FBVs_AqBFY+0ExnHsnA9BDRwuOsHpxRL+rLuCsuxP5t5Jg@mail.gmail.com>
Wells Oliver <wells.oliver@gmail.com> writes:
> 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?
Looking for aggtranstype = 'anyarray'::regtype would give you a hit list,
but beware that not every one of those was changed. Looking at HEAD,
I see
postgres=# select aggfnoid::regprocedure from pg_aggregate where aggtranstype = 'anyarray'::regtype;
aggfnoid
---------------
max(anyarray)
min(anyarray)
(2 rows)
so you'd want to exclude those. (I guess just skipping ones with oid <
9999 would be enough to skip built-ins.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, wells.oliver@gmail.com
Subject: Re: Struggling with 13->14 and anyarray -> anycompatiblearray
In-Reply-To: <2491000.1667597489@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox