mirror of
https://github.com/postgres/postgres.git
synced 2026-02-19 02:29:10 -05:00
843d2879aa
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 |
||
|---|---|---|
| .. | ||
| bit.out | ||
| bytea.out | ||
| char.out | ||
| cidr.out | ||
| date.out | ||
| enum.out | ||
| float4.out | ||
| float8.out | ||
| inet.out | ||
| install_btree_gin.out | ||
| int2.out | ||
| int4.out | ||
| int8.out | ||
| interval.out | ||
| macaddr.out | ||
| macaddr8.out | ||
| money.out | ||
| numeric.out | ||
| oid.out | ||
| text.out | ||
| time.out | ||
| timestamp.out | ||
| timestamptz.out | ||
| timetz.out | ||
| varbit.out | ||
| varchar.out | ||