Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1or4Ho-0003uv-4S for pgsql-admin@arkaria.postgresql.org; Fri, 04 Nov 2022 21:31:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1or4Hm-0008M8-Bh for pgsql-admin@arkaria.postgresql.org; Fri, 04 Nov 2022 21:31:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1or4Hm-0008Ly-0r for pgsql-admin@lists.postgresql.org; Fri, 04 Nov 2022 21:31:34 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1or4Hj-000577-KN for pgsql-admin@postgresql.org; Fri, 04 Nov 2022 21:31:32 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2A4LVTXN2491001; Fri, 4 Nov 2022 17:31:29 -0400 From: Tom Lane To: Wells Oliver cc: pgsql-admin Subject: Re: Struggling with 13->14 and anyarray -> anycompatiblearray In-reply-to: References: <2475533.1667589169@sss.pgh.pa.us> Comments: In-reply-to Wells Oliver message dated "Fri, 04 Nov 2022 13:51:59 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2490999.1667597489.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 04 Nov 2022 17:31:29 -0400 Message-ID: <2491000.1667597489@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Wells Oliver 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 arra= y > function might be looking for anyarray and need to be dropped/re-created > with anycompatiblearray? Looking for aggtranstype =3D 'anyarray'::regtype would give you a hit list= , but beware that not every one of those was changed. Looking at HEAD, I see postgres=3D# select aggfnoid::regprocedure from pg_aggregate where aggtran= stype =3D '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