postgresql/contrib/btree_gin/expected
Tom Lane a6bd28beb0 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
2021-08-10 18:10:29 -04:00
..
bit.out
bool.out Add support of bool, bpchar, name and uuid to btree_gin 2018-04-05 18:19:10 +03:00
bpchar.out Add support of bool, bpchar, name and uuid to btree_gin 2018-04-05 18:19:10 +03:00
bytea.out
char.out Fix failure of btree_gin indexscans with "char" type and </<= operators. 2021-08-10 18:10:29 -04:00
cidr.out
date.out
enum.out Add btree_gin support for enum types 2017-03-21 11:04:17 -04:00
float4.out
float8.out
inet.out
install_btree_gin.out
int2.out
int4.out
int8.out
interval.out
macaddr8.out Add support for EUI-64 MAC addresses as macaddr8 2017-03-15 11:16:25 -04:00
macaddr.out
money.out
name.out Add support of bool, bpchar, name and uuid to btree_gin 2018-04-05 18:19:10 +03:00
numeric.out
oid.out
text.out
time.out
timestamp.out
timestamptz.out
timetz.out
uuid.out Add support of bool, bpchar, name and uuid to btree_gin 2018-04-05 18:19:10 +03:00
varbit.out
varchar.out