aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2024-06-13 20:34:42 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2024-06-13 20:35:02 -0400
commit56a8296212b68267dc2bddeb1fb40a893b1aadb3 (patch)
treea03c58f08fba5f51859f66f0959efa92adf481bb /doc/src
parentd872e1b4730b793c9d72c80b65feb988269104e2 (diff)
downloadpostgresql-56a8296212b68267dc2bddeb1fb40a893b1aadb3.tar.gz
postgresql-56a8296212b68267dc2bddeb1fb40a893b1aadb3.zip
Fix parsing of ignored operators in websearch_to_tsquery().
The manual says clearly that punctuation in the input of websearch_to_tsquery() is ignored, except for the special cases of dashes and quotes. However, this failed for cases like "(foo bar) or something", or in general an ISOPERATOR character in front of the "or". We'd switch back to WAITOPERAND state, then ignore the operator character while remaining in that state, and then reach the "or" in WAITOPERAND state which (intentionally) makes us treat it as data. The fix is simple enough: if we see an ISOPERATOR character while in WAITOPERATOR state, we have to skip it while staying in that state. (We don't need to worry about other punctuation characters: those will be consumed as though they were words, but then rejected by lexizing.) In v14 and up (since commit eb086056f) we can simplify the code a bit more too, because there is no longer a reason for the WAITOPERAND state to distinguish between quoted and unquoted operands. Per bug #18479 from Manos Emmanouilidis. Back-patch to all supported branches. Discussion: https://postgr.es/m/18479-d9b46e2fc242c33e@postgresql.org
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions