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 1s7KDX-0051ot-9I for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2024 19:23:12 +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 1s7KDX-005KBJ-3H for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2024 19:23:11 +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 1s7KDW-005KBB-Hg for pgsql-hackers@lists.postgresql.org; Wed, 15 May 2024 19:23:10 +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 1s7KDS-000Pq2-Hc for pgsql-hackers@lists.postgresql.org; Wed, 15 May 2024 19:23:09 +0000 Received: from localhost (localhost [127.0.0.1]) by 008.lax.mailroute.net (Postfix) with ESMTP id 4Vfjmm74jtz6Cnk8t; Wed, 15 May 2024 19:23:04 +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= 1715800982; x=1718392983; bh=vwTC3lIxInrCAdqJ9h8NgE/t2K/fMcbzQku j2fspBXw=; b=4Ih4l+4R3oQeiQtXwRiBR3/2+iwDsmhmKJ2rvNw36p5BELDZGND JVF7nGcIjXPXaSeIMidhv3TYqT1dxBsdiehqM7+05VWa0dToZne4LWdOKMDMOVT4 jPWokXuYprV8K1+TN/RMJPu3Cqtkpl/ZFmG+vK7x9/92ZcuZqFHOgR/XYVC9u+Zi FwcByL44bFoAdhDkp8iVjOFseiOZTW+Dno2yr53h8zBuHrIW89z89XkiPPoHVs34 6OeytsvYPRaJD7mrVtHVet0QeRoZmddt3ZlHSRFPM2s3yAfgBI5B2g4/GA75yAJd G2E1dDm1cwIGlURd3/b9yIl9zMmDL4GAqoA== 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 Wn-YiYVj7TLW; Wed, 15 May 2024 19:23:02 +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 4Vfjmh4TLzz6Cnk8s; Wed, 15 May 2024 19:23:00 +0000 (UTC) Subject: Re: add function argument names to regex* functions. To: Robert Haas , "David G. Johnston" References: <0eb3a5d7-75d8-4da5-9c88-a93deccdaa03@gmail.com> <75129a34-14da-48aa-9906-42062fe78664@gmail.com> <1763682.1712090733@sss.pgh.pa.us> Cc: jian he , Tom Lane , Peter Eisentraut , Dian Fay , Jim Nasby , PostgreSQL Hackers From: Chapman Flack Message-ID: <66450B93.2070904@acm.org> Date: Wed, 15 May 2024 15:22:59 -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=utf-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 05/15/24 15:07, Robert Haas wrote: > is. I believe that if I were reading the documentation, count would be > clearer to me than N, N would probably still be clear enough, and > replace_at wouldn't be clear at all. I'd expect replace_at to be a > character position or something, not an occurrence count. You've said the magic word. In the analogous (but XQuery-based) ISO standard regex functions, the argument that does that is identified with the keyword OCCURRENCE. What would be wrong with that, for consistency's sake? Regards, -Chap