diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-02-18 22:38:55 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-02-18 22:38:55 -0500 |
| commit | bf9d3a5f847e91154b7cde255da7f24cd129ff35 (patch) | |
| tree | 4765586802623d5965f08899b45dda23063e5ab5 /src/backend/regex/regc_lex.c | |
| parent | d4b667e9353a70c4ee2847603e5ad2e14e20f82e (diff) | |
| download | postgresql-bf9d3a5f847e91154b7cde255da7f24cd129ff35.tar.gz postgresql-bf9d3a5f847e91154b7cde255da7f24cd129ff35.zip | |
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/regc_lex.c')
| -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); |