Re: BUG #18956: Observing an issue in regexp_count()
От | Tom Lane |
---|---|
Тема | Re: BUG #18956: Observing an issue in regexp_count() |
Дата | |
Msg-id | 1203062.1749736486@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | BUG #18956: Observing an issue in regexp_count() (PG Bug reporting form <noreply@postgresql.org>) |
Ответы |
Re: BUG #18956: Observing an issue in regexp_count()
|
Список | pgsql-bugs |
hubert depesz lubaczewski <depesz@depesz.com> writes: > On Thu, Jun 12, 2025 at 08:03:25AM +0000, PG Bug reporting form wrote: >> I am trying to run the below query >> select REGEXP_COUNT('cat at the flat', '\Bat\b') ; >> I was expecting it to return 2 but I see Postgres is returning 0. I see that >> there are two matches, cat and flat. All it should do is to look for the >> word at whose left side shoudn't be a word boundary while the right side >> should be a word boundary > What makes you think that \B/\b has anything to do with word boundary? Indeed, they do not. > As far as I can tell pg regexps have nothing related to word boundaries. Sure we do, see "Regular Expression Constraint Escapes": https://www.postgresql.org/docs/current/functions-matching.html#POSIX-CONSTRAINT-ESCAPES-TABLE Unfortunately, since these are all way outside the POSIX regexp standard, different systems have implemented these extensions differently. I don't doubt that \B/\b mean word boundaries in some other system. regards, tom lane
В списке pgsql-bugs по дате отправления: