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 | ab208421eeb785fc72a3e7fc1122127029165392 (patch) | |
| tree | 98841f3ff91daec9ffa570bb7512a35484a29619 /src/backend/regex/regc_pg_locale.c | |
| parent | 618d139f82d4222df796e989de3c4c4de0359d7b (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/regc_pg_locale.c')
0 files changed, 0 insertions, 0 deletions