Re: Re: [PATCH] regexp_positions ( string text, pattern text, flags text ) → setof int4range[] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [PATCH] regexp_positions ( string text, pattern text, flags text ) → setof int4range[]
Date
Msg-id 2071665.1630504971@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] regexp_positions ( string text, pattern text, flags text ) → setof int4range[]  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: [PATCH] regexp_positions ( string text, pattern text, flags text ) → setof int4range[]  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
Daniel Gustafsson <daniel@yesql.se> writes:
>> On 9 Mar 2021, at 20:30, Joel Jacobson <joel@compiler.org> wrote:
>> Attached is a patch implementing it this way.

> This patch no longer applies, can you please submit a rebased version?

Also, since 642433707 ("This patch adds new functions regexp_count(),
regexp_instr(), regexp_like(), and regexp_substr(), and extends
regexp_replace() with some new optional arguments") is already in,
we need to think about how this interacts with that.  Do we even
still need any more functionality in this area?  Should we try to
align the APIs?

Those new function APIs have some Oracle-isms that I don't especially
care for, like use of int for what should be a boolean.  Still, users
aren't going to give us a pass for wildly inconsistent APIs just because
some functions came from Oracle and some didn't.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: dup(0) fails on Ubuntu 20.04 and macOS 10.15 with 13.0
Next
From: Fujii Masao
Date:
Subject: Re: Add statistics refresh materialized view