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

From: er(at)xs4all(dot)nl
To: Gilles Darold <gilles(at)darold(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Chapman Flack <chap(at)anastigmatix(dot)net>
Subject: Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace
Date: 2021-03-21 11:07:37
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 2021.03.20. 19:48 Gilles Darold <gilles(at)darold(dot)net> wrote:
> This is a new version of the patch that now implements all the XQUERY
> regexp functions as described in the standard, minus the differences of
> PostgerSQL regular expression explain in [1].
> The standard SQL describe functions like_regex(), occurrences_regex(),
> position_regex(), substring_regex() and translate_regex() which
> correspond to the commonly named functions regexp_like(),
> regexp_count(), regexp_instr(), regexp_substr() and regexp_replace() as
> reported by Chapman Flack in [2]. All these function are implemented in

> [v2-0001-xquery-regexp-functions.patch]


Apply, compile and (world)check are fine. I haven't found errors in functionality.

I went through the docs, and came up with these changes in func.sgml, and pg_proc.dat.

Useful functions - thanks!

Erik Rijkers

Attachment Content-Type Size
func.sgml.20210321.diff text/x-patch 7.2 KB
pg_proc.dat.20210321.diff text/x-patch 1.8 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2021-03-21 11:47:12 Re: pg_upgrade failing for 200+ million Large Objects
Previous Message 2021-03-21 10:58:20 RE: [HACKERS] logical decoding of two-phase transactions