Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gilles Darold <gilles(at)darold(dot)net>
Cc: Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers(at)lists(dot)postgresql(dot)org, chap(at)anastigmatix(dot)net
Subject: Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace
Date: 2021-12-15 12:41:16
Message-ID: b7988566-daa2-80ed-2fdc-6f6630462d26@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03.08.21 19:10, Tom Lane wrote:
> Gilles Darold <gilles(at)darold(dot)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?

Attachment Content-Type Size
0001-doc-More-documentation-on-regular-expressions-and-SQ.patch text/plain 6.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2021-12-15 12:51:44 Re: Failed transaction statistics to measure the logical replication progress
Previous Message Shay Rojansky 2021-12-15 12:35:24 Privilege required for IF EXISTS event if the object already exists