Tom Lane 042c9091f0 Produce more-optimal plans for bitmap scans on boolean columns. ... The planner simplifies boolean comparisons such as "x = true" and "x = false" down to "x" and "NOT x" respectively, to have a canonical form to ease comparisons. However, if we want to use an index on x, the index AM APIs require us to reconstitute the comparison-operator form of the indexqual. While that works, in bitmap indexscans the canonical form of the qual was emitted as a "filter" condition although it really only needs to be a "recheck" condition, because create_bitmap_scan_plan didn't recognize the equivalence of that form with the generated indexqual. booleq() is pretty cheap so that likely doesn't make very much difference, but it's unsightly so let's clean it up. To fix, add a case to predicate_implied_by() to recognize the equivalence of such clauses. This is a relatively low-cost place to add a check, and perhaps it will have additional use cases in future. Richard Guo and Tom Lane, per discussion of bug #17618 from Sindy Senorita. Discussion: https://postgr.es/m/17618-7a2240bfaa7e84ae@postgresql.org		2022-11-08 10:36:04 -05:00
..
bit.out
bool.out	Produce more-optimal plans for bitmap scans on boolean columns.	2022-11-08 10:36:04 -05:00
bpchar.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
macaddr8.out
macaddr.out
money.out
name.out
numeric.out
oid.out
text.out
time.out
timestamp.out
timestamptz.out
timetz.out
uuid.out
varbit.out
varchar.out