| Ticket UUID: | 884d0ac78cbab248d054ec96d13c2a741bb0a94c | ||
| Title: | Unexpected string-start constraint match in middle of string after newline | ||
| Type: | Bug | Created on: | 2017-12-28 00:52:02 |
| Submitter: | dkf | Assigned to: | nobody |
| Subsystem: | 43. Regexp | Severity: | Minor |
| Priority: | 5 Medium | Last modified: | 2021-02-20 21:37:20 |
| Status: | Open | Closed by: | nobody |
| Resolution: | None | Closed on: | |
| Version: | core-8-6-branch tip, 28-Dec-2017 | ||
| Description: | ||||
|
If you do:
regexp -all {^|\n} "foo\nbar"
then it returns 3. I'd expect that (perhaps) with the -line option, but in standard mode that is rather "surprising" as there is only one place where the string starts and only one newline character.
| ||||
| User Comments: | ||||
dkf added on 2017-12-28 12:47:54:
A consequence of this issue is this: % puts [regsub -all "^|\n" "foo\nbar" "\nXX"] XXfoo XX XXbarThe double substitution of \nXX before bar is again "unexpected". tgl added on 2021-02-20 21:37:20:
FWIW, I can't reproduce this misbehavior in current Postgres: I get a correct-looking result from
# select regexp_replace(E'foo\nbar', '^|\n', E'\nXX', 'g');
regexp_replace
----------------
+
XXfoo +
XXbar
(1 row)
I speculate that it got fixed as a side-effect of the constraint loop fixes we did awhile ago.
I thought you guys had absorbed those, though.
| ||||