Tom Lane b5febc1d12 Fix IOS planning when only some index columns can return an attribute. ... Since 9.5, it's possible that some but not all columns of an index support returning the indexed value for index-only scans. If the same indexed column appears in index columns that behave both ways, check_index_only() supposed that it'd be OK to do an index-only scan testing that column; but that fails if we have to recheck the indexed condition on one of the columns that doesn't support this. In principle we could make this work by remapping the recheck expressions to pull the value from a column that does support returning the indexed value. But such cases are so weird and rare that, at least for now, it doesn't seem worth the trouble. Instead, just teach check_index_only that a value is returnable only if all the index columns containing it are returnable, rather than any of them. Per report from David Pereiro Lagares. Back-patch to 9.5 where the possibility of this situation appeared. Kyotaro Horiguchi Discussion: https://postgr.es/m/1516210494.1798.16.camel@nlpgo.com		2018-03-01 15:35:03 -05:00
..
bit.out
bytea.out
cash.out
char_1.out
char.out
cidr.out
date.out
enum.out	Add btree_gist support for enum types.	2017-03-21 10:43:27 -04:00
float4.out
float8.out
inet.out	Fix IOS planning when only some index columns can return an attribute.	2018-03-01 15:35:03 -05:00
init.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
not_equal.out
numeric.out
oid.out
text_1.out
text.out
time.out
timestamp.out
timestamptz.out
timetz.out
uuid.out
varbit.out
varchar_1.out
varchar.out