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 1oCv69-0002Pj-Eh for pgsql-hackers@arkaria.postgresql.org; Sun, 17 Jul 2022 03:37:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oCv68-00034R-C7 for pgsql-hackers@arkaria.postgresql.org; Sun, 17 Jul 2022 03:37:36 +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 1oCv68-0002za-2r for pgsql-hackers@lists.postgresql.org; Sun, 17 Jul 2022 03:37:36 +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 1oCv65-0005DE-UZ for pgsql-hackers@lists.postgresql.org; Sun, 17 Jul 2022 03:37:35 +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 26H3bQGK4077926; Sat, 16 Jul 2022 23:37:26 -0400 From: Tom Lane To: Martin Kalcher cc: Thomas Munro , PostgreSQL Hackers Subject: Re: Proposal to introduce a shuffle function to intarray extension In-reply-to: <4073858.1658027909@sss.pgh.pa.us> References: <9d160a44-7675-51e8-60cf-6d64b76db831@aboutsource.net> <4073858.1658027909@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Sat, 16 Jul 2022 23:18:29 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4077924.1658029046.1@sss.pgh.pa.us> Date: Sat, 16 Jul 2022 23:37:26 -0400 Message-ID: <4077925.1658029046@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I wrote: > On the whole, I'd vote for calling it shuffle(), and expecting that > we'd also use that name for any future generic version. Actually ... is there a reason to bother with an intarray version at all, rather than going straight for an in-core anyarray function? It's not obvious to me that an int4-only version would have major performance advantages. regards, tom lane