Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace
Date
Msg-id 81423aa1-154f-7cc7-5709-d6c040261ceb@enterprisedb.com
Whole thread Raw
In response to Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace  (Gilles Darold <gilles@darold.net>)
List pgsql-hackers
On 15.12.21 14:15, Gilles Darold wrote:
> Le 15/12/2021 à 13:41, Peter Eisentraut a écrit :
>> On 03.08.21 19:10, Tom Lane wrote:
>>> Gilles Darold <gilles@darold.net> writes:
>>>> Sorry I have missed that, but I'm fine with this implemenation so let's
>>>> keep the v6 version of the patch and drop this one.
>>>
>>> Pushed, then.  There's still lots of time to tweak the behavior of 
>>> course.
>>
>> I have a documentation follow-up to this.  It seems that these new 
>> functions are almost a de facto standard, whereas the SQL-standard 
>> functions are not implemented anywhere.  I propose the attached patch 
>> to update the subsection in the pattern-matching section to give more 
>> detail on this and suggest equivalent functions among these newly 
>> added ones.  What do you think?
> 
> 
> I'm in favor to apply your changes to documentation. It is a good thing 
> to precise the relation between this implementation of the regex_* 
> functions and the SQL stardard.

ok, done



pgsql-hackers by date:

Previous
From: "osumi.takamichi@fujitsu.com"
Date:
Subject: RE: Failed transaction statistics to measure the logical replication progress
Next
From: Amit Kapila
Date:
Subject: Re: row filtering for logical replication