| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gilles Darold <gilles(at)migops(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] fix references to like_regex |
| Date: | 2021-11-02 15:50:47 |
| Message-ID: | 1513225.1635868247@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gilles Darold <gilles(at)migops(dot)com> writes:
> Since we have the regexp_like operator I have found that there is two
> references in the documentation about PostgreSQL lacking of LIKE_REGEX
> implementation. Here is a patch to fix the documentation. I simply
> remove the reference to non exist of LIKE_REGEX in PostgreSQL in chapter
> "9.7.3.8 Differences from XQuery" And try to modify chapter "9.16.2.3.
> SQL/JSON Regular Expressions" to mention the REGEXP_LIKE operator. For
> the second fix there should be better wording.
I don't think we should change these (yet). regexp_like() is *not*
LIKE_REGEX, precisely because it's using a slightly different
regular-expression language than what the spec calls for.
At some point we may provide a skin for the regexp engine that
duplicates the spec's definition, and then we can implement
LIKE_REGEX for real.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-11-02 15:55:23 | Re: should we enable log_checkpoints out of the box? |
| Previous Message | Bossart, Nathan | 2021-11-02 15:39:38 | Re: inefficient loop in StandbyReleaseLockList() |