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 1sTMyP-00FXPy-Ne for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Jul 2024 14:46:41 +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 1sTMyO-00AlVt-2z for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Jul 2024 14:46:40 +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 1sTMyN-00AlVl-El for pgsql-hackers@lists.postgresql.org; Mon, 15 Jul 2024 14:46:39 +0000 Received: from 008.lax.mailroute.net ([199.89.1.11]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sTMyK-002FbD-Ip for pgsql-hackers@lists.postgresql.org; Mon, 15 Jul 2024 14:46:38 +0000 Received: from localhost (localhost [127.0.0.1]) by 008.lax.mailroute.net (Postfix) with ESMTP id 4WN4lZ0cvsz6Cp2tZ; Mon, 15 Jul 2024 14:46:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=acm.org; h= content-transfer-encoding:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject:received:received; s=mr01; t= 1721054791; x=1723646792; bh=f0/unWiLBML6wsH6gtBn6kBQYlTDnu7PBPi MSkvsB9I=; b=Dt97iOlubdROTATCd+YFQ7gGXzPKl5lNDUHVA97JYKk2h3sl6Dg Ro96PQexDQPNCt72tqKL4xJYt0nhHTfz2vWRX4wW0sIqMRoRTXbTgcxcDiW/1hxB YwnpKEc5CYei9znHwrKHFWUy5V+6DydXyVpUImp9VpmbGUAee0HjxBVK4xAUTm7m UxisH0SBb4TrQ304ACvmiwUMawgE0BO/A8K7mc1cgiKrn+uOOUUdF/iOYkEbCVuP 8jBGo0EsrtuKIZgqf04TBUiNviLxtGV5xcy21/3pZwTCJemBQL36pWcdEXMsZQNB H3CFE0tC2rvRyTTRLNF7ODLg5xrde71T5Eg== X-Virus-Scanned: by MailRoute Received: from 008.lax.mailroute.net ([127.0.0.1]) by localhost (008.lax [127.0.0.1]) (mroute_mailscanner, port 10029) with LMTP id 2AR59_M1dB-A; Mon, 15 Jul 2024 14:46:31 +0000 (UTC) Received: from [73.103.120.3] (c-73-103-120-3.hsd1.in.comcast.net [73.103.120.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jcflack@acm.org) by 008.lax.mailroute.net (Postfix) with ESMTPSA id 4WN4lV0r1Zz6Cnv3g; Mon, 15 Jul 2024 14:46:29 +0000 (UTC) Subject: Re: add function argument names to regex* functions. To: jian he , Tom Lane References: <0eb3a5d7-75d8-4da5-9c88-a93deccdaa03@gmail.com> <75129a34-14da-48aa-9906-42062fe78664@gmail.com> <1763682.1712090733@sss.pgh.pa.us> <1816377.1715800208@sss.pgh.pa.us> Cc: Robert Haas , Peter Eisentraut , Dian Fay , Jim Nasby , PostgreSQL Hackers From: Chapman Flack X-Enigmail-Draft-Status: N1110 Message-ID: <6695362E.4010202@acm.org> Date: Mon, 15 Jul 2024 10:46:06 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 07/15/24 08:02, jian he wrote: > also address Chapman Flack point: > correct me if i am wrong, but i don't think the ISO standard mandates > function argument names. > So we can choose the best function argument name for our purpose? Ah, I may have mistaken which functions the patch meant to apply to. These being the non-ISO regexp_* functions using POSIX expressions, the ISO standard indeed says nothing about them. In the ISO standard *_regex "functions", there are not really "function argument names" mandated, because, like so many things in ISO SQL, they have their own special syntax instead of being generic function calls: TRANSLATE_REGEX('a|e|i|o|u' FLAG 'i' IN 'A PostgreSQL function' WITH 'X' FROM 1 OCCURRENCE 3); Any choice to use similar argument names in the regexp_* functions would be a matter of consistency with the analogous ISO functions, not anything mandated. Regards, -Chap