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.sql
bytea.sql
cash.sql
char.sql
cidr.sql
date.sql
enum.sql	Add btree_gist support for enum types.	2017-03-21 10:43:27 -04:00
float4.sql
float8.sql
inet.sql	Fix IOS planning when only some index columns can return an attribute.	2018-03-01 15:35:03 -05:00
init.sql	Test all contrib-created operator classes with amvalidate.	2016-11-29 15:05:22 -05:00
int2.sql
int4.sql
int8.sql
interval.sql	Properly initialize SortSupport for ORDER BY rechecks in nodeIndexscan.c.	2016-06-05 11:53:06 -04:00
macaddr8.sql	Add support for EUI-64 MAC addresses as macaddr8	2017-03-15 11:16:25 -04:00
macaddr.sql
not_equal.sql	Ensure plan stability in contrib/btree_gist regression test.	2016-05-12 20:04:38 -04:00
numeric.sql
oid.sql
text.sql
time.sql
timestamp.sql
timestamptz.sql
timetz.sql
uuid.sql	Add uuid to the set of types supported by contrib/btree_gist.	2016-11-29 14:08:34 -05:00
varbit.sql
varchar.sql