Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tMWZs-004lnh-P2 for pgsql-hackers@arkaria.postgresql.org; Sat, 14 Dec 2024 18:09:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tMWR2-005PQa-To for pgsql-hackers@arkaria.postgresql.org; Sat, 14 Dec 2024 18:00:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tMWR2-005PQR-JC for pgsql-hackers@lists.postgresql.org; Sat, 14 Dec 2024 18:00:13 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tMWQx-002qNS-7t for pgsql-hackers@lists.postgresql.org; Sat, 14 Dec 2024 18:00:13 +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 4BEI00oX1400206; Sat, 14 Dec 2024 13:00:00 -0500 From: Tom Lane To: Michael Paquier cc: Ronan Dunklau , pgsql-hackers@lists.postgresql.org, Peter Eisentraut Subject: Re: Converting contrib SQL functions to new style In-reply-to: References: <3395418.1618352794@sss.pgh.pa.us> <2345099.ElGaqSPkdT@aivenlaptop> Comments: In-reply-to Michael Paquier message dated "Thu, 14 Nov 2024 13:30:43 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1400204.1734199200.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sat, 14 Dec 2024 13:00:00 -0500 Message-ID: <1400205.1734199200@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > Doing that step-by-step is better than nothing, hence limiting the use > of named parameters for only the functions whose body is rewritten is > fine by me, as a first step, as long as the names are used rather the > dollar parameter numbers. I'd suggest to do take the bonus step of > applying the same rule to all the other functions so as everything > applies with the same extension update in a single major release. > Perhaps on top of the patches already proposed? There is no need for > an extra version bump if all that is done in the same development > cycle. FWIW, I don't agree at all with doing argument name addition in this patchset. Certainly that's a fine thing to do, but it's an independent issue and should be handled in an independent patch. I see that the cfbot is unhappy because it doesn't understand that some of the patches have been applied already. I am going to go ahead and get the earthdistance one done, because we have a live problem report about that [1]. I'll rebase and repost the remainder afterwards. regards, tom lane [1] https://www.postgresql.org/message-id/flat/6a6439f1-8039-44e2-8fb9-590= 28f7f2014%40mailbox.org