diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-02-12 16:26:47 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-02-12 16:26:47 -0500 |
commit | 0347470b31c139aa4f1d366fbdb85f32b7f82ad0 (patch) | |
tree | 1a88c7d8b4e34175dc0a5d57ca2776ad5e106f34 /src/backend/executor/nodeFunctionscan.c | |
parent | 5b2945ec0a39959962072c39d1817d0fdf23d486 (diff) | |
download | postgresql-0347470b31c139aa4f1d366fbdb85f32b7f82ad0.tar.gz postgresql-0347470b31c139aa4f1d366fbdb85f32b7f82ad0.zip |
Avoid divide-by-zero in regex_selectivity() with long fixed prefix.
Given a regex pattern with a very long fixed prefix (approaching 500
characters), the result of pow(FIXED_CHAR_SEL, fixed_prefix_len) can
underflow to zero. Typically the preceding selectivity calculation
would have underflowed as well, so that we compute 0/0 and get NaN.
In released branches this leads to an assertion failure later on.
That doesn't happen in HEAD, for reasons I've not explored yet,
but it's surely still a bug.
To fix, just skip the division when the pow() result is zero, so
that we'll (most likely) return a zero selectivity estimate. In
the edge cases where "sel" didn't yet underflow, perhaps this
isn't desirable, but I'm not sure that the case is worth spending
a lot of effort on. The results of regex_selectivity_sub() are
barely worth the electrons they're written on anyway :-(
Per report from Alexander Lakhin. Back-patch to all supported versions.
Discussion: https://postgr.es/m/6de0a0c3-ada9-cd0c-3e4e-2fa9964b41e3@gmail.com
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions