diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-10 18:10:29 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-10 18:10:29 -0400 |
| commit | a6bd28beb0639d4cf424e961862a65c466ca65bf (patch) | |
| tree | 836db5b4b9079c8ff479624f823afe791ebb2b1e /src/backend/executor/nodeModifyTable.c | |
| parent | 72bbff4cd6eaf55239ccef79cec61766b5f8f1d2 (diff) | |
| download | postgresql-a6bd28beb0639d4cf424e961862a65c466ca65bf.tar.gz postgresql-a6bd28beb0639d4cf424e961862a65c466ca65bf.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/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions