database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-26 12:21:12 +03:00
Code Activity

Fix regexp_matches() handling of zero-length matches.

Browse Source 
We'd find the same match twice if it was of zero length and not immediately
adjacent to the previous match.  replace_text_regexp() got similar cases
right, so adjust this search logic to match that.  Note that even though
the regexp_split_to_xxx() functions share this code, they did not display
equivalent misbehavior, because the second match would be considered
degenerate and ignored.

Jeevan Chalke, with some cosmetic changes by me.
This commit is contained in:
Tom Lane
2013-07-31 11:31:22 -04:00
parent c876fb4241
commit d074b4e50d
4 changed files with 75 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
src/backend/utils/adt/varlena.c
View File

@ -3083,7 +3083,10 @@ replace_text_regexp(text *src_text, void *regexp,
break;
/*
* Search from next character when the matching text is zero width.
* Advance search position. Normally we start the next search at the
* end of the previous match; but if the match was of zero length, we
* have to advance by one character, or we'd just find the same match
* again.
*/
search_start = data_pos;
if (pmatch[0].rm_so == pmatch[0].rm_eo)