diff options
| author | Tom Lane | 2021-02-19 03:38:55 +0000 |
|---|---|---|
| committer | Tom Lane | 2021-02-19 03:38:55 +0000 |
| commit | b5a66e7353ba65c11c5fc6a79b72213bde8dbe44 (patch) | |
| tree | 33b57ccfd288547ddad91b19381c9abe65a115b9 /src/backend/regex | |
| parent | 614b7f18b3bda738f352a8732cf749eb5fa56dae (diff) | |
Fix another ancient bug in parsing of BRE-mode regular expressions.
While poking at the regex code, I happened to notice that the bug
squashed in commit afcc8772e had a sibling: next() failed to return
a specific value associated with the '}' token for a "\{m,n\}"
quantifier when parsing in basic RE mode. Again, this could result
in treating the quantifier as non-greedy, which it never should be in
basic mode. For that to happen, the last character before "\}" that
sets "nextvalue" would have to set it to zero, or it'd have to have
accidentally been zero from the start. The failure can be provoked
repeatably with, for example, a bound ending in digit "0".
Like the previous patch, back-patch all the way.
Diffstat (limited to 'src/backend/regex')
| -rw-r--r-- | src/backend/regex/regc_lex.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/regex/regc_lex.c b/src/backend/regex/regc_lex.c index ca2bce48312..16664531641 100644 --- a/src/backend/regex/regc_lex.c +++ b/src/backend/regex/regc_lex.c @@ -389,7 +389,7 @@ next(struct vars *v) { v->now++; INTOCON(L_BRE); - RET('}'); + RETV('}', 1); } else FAILW(REG_BADBR); |