diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-10 18:10:30 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-10 18:10:30 -0400 |
| commit | 7ba487cf90071717c9c352dc074a9140860eba55 (patch) | |
| tree | f2c367a9c5507ef1ad7bfa120a886a61187ce1d1 /src/backend/regex/regexec.c | |
| parent | e849f3f1f884ad140b60a24354c6371cbd2efbb6 (diff) | |
| download | postgresql-7ba487cf90071717c9c352dc074a9140860eba55.tar.gz postgresql-7ba487cf90071717c9c352dc074a9140860eba55.zip | |
Fix failure of btree_gin indexscans with "char" type and </<= operators.
As a result of confusion about whether the "char" type is signed or
unsigned, scans for index searches like "col < 'x'" or "col <= 'x'"
would start at the middle of the index not the left end, thus missing
many or all of the entries they should find. Fortunately, this
is not a symptom of index corruption. It's only the search logic
that is broken, and we can fix it without unpleasant side-effects.
Per report from Jason Kim. This has been wrong since btree_gin's
beginning, so back-patch to all supported branches.
Discussion: https://postgr.es/m/20210810001649.htnltbh7c63re42p@jasonk.me
Diffstat (limited to 'src/backend/regex/regexec.c')
0 files changed, 0 insertions, 0 deletions