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 1rIcKu-009m4z-VX for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Dec 2023 22:25: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 1rIcKt-00AKMX-Ka for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Dec 2023 22:25:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rIcKt-00AKMP-Am for pgsql-hackers@lists.postgresql.org; Wed, 27 Dec 2023 22:25:11 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rIcKr-00CVPe-3M for pgsql-hackers@lists.postgresql.org; Wed, 27 Dec 2023 22:25:10 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id C64773200A3B; Wed, 27 Dec 2023 17:25:07 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 27 Dec 2023 17:25:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1703715907; x=1703802307; bh=eBjsVdStczeTNZNbnbo+u/8UPu5FjuI+E175VPGTcYM=; b= Cb+95JRjilbQDQwQ7i4uyC4Dc2hYnUj/W9Et100FAoEk1t64JOGHmchcHb9bQDkO zhZ6Sc14mai+KKa4Uo5fj9WVPn/siCcRAqYeCd8vaAVtk25e5aK7oCBgt1NMTQ1r JgZUFRi/FJlAYccVyvO87EE3VE8fXRtZHDQT3jFJ4aYPSikbD8goid+nOVcMRVen uth5m7RR3++vB4SOevhASnbYmL8OYUapWh3CWJQEqVJIKFhDsZc2WTgpW103z8mx U/KkKT8eWOqXeqjJI9TVg7F8MrhlaeWK57+72c5ZmTCSsCcV1T0PlNspVPgM0/K8 lw2Wg7l/kQYRRFR8Qo5/6w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1703715907; x= 1703802307; bh=eBjsVdStczeTNZNbnbo+u/8UPu5FjuI+E175VPGTcYM=; b=R Q3gQFgt99c+euJv7OXW2sar/ig5ksOgPfH30H1EtKAGTGw867GDXWGrb7K5hU/J9 xLzp8GzSzJ8N2A/HhFFBC9+hyRmED+J0j5B1p6uWUSnbp1BeHtunZNOMrkTOGcRx BnihjcGjA0k2954dhwj1FWniqz3iK6cpXQ/JINabSyHaS4Stnh6hUvy8HYsU6GlS hFXqvH00Z/3mL810pN9VfJIJcGb0eMCpfs0BwVHP0jIOjMCi2gn2L7r2QJlrYGAG KhAsl9HL5eX2+F6Y3ryofxKwFJgd7y2WI6DzRYUVoHG52S+T0Dz7IQiv4sJ3sEdX Hs7uv75a/1LAi+1blzV/g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvddvledgudeifecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh eqnecuggftrfgrthhtvghrnhepheeivdfhuefhueeggfefheegjedtveeuhfethfeufedv udfgtdeuhefgfeduhfffnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 27 Dec 2023 17:25:06 -0500 (EST) Message-ID: Date: Wed, 27 Dec 2023 23:25:05 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: add function argument names to regex* functions. Content-Language: en-US To: jian he , PostgreSQL Hackers References: From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 27.12.23 17:53, jian he wrote: > similar to [1], add function argument names to the following functions: > regexp_like, regexp_match,regexp_matches,regexp_replace, > regexp_substr,regexp_split_to_array,regexp_split_to_table,regexp_count Note that these functions are a quasi-standard that is shared with other SQL implementations. It might be worth looking around if there are already other implementations of this idea.