mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-24 18:55:04 +08:00
b5febc1d12
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 |
||
|---|---|---|
| .. | ||
| data | ||
| expected | ||
| sql | ||
| .gitignore | ||
| btree_bit.c | ||
| btree_bytea.c | ||
| btree_cash.c | ||
| btree_date.c | ||
| btree_enum.c | ||
| btree_float4.c | ||
| btree_float8.c | ||
| btree_gist--1.0--1.1.sql | ||
| btree_gist--1.1--1.2.sql | ||
| btree_gist--1.2--1.3.sql | ||
| btree_gist--1.2.sql | ||
| btree_gist--1.3--1.4.sql | ||
| btree_gist--1.4--1.5.sql | ||
| btree_gist--unpackaged--1.0.sql | ||
| btree_gist.c | ||
| btree_gist.control | ||
| btree_gist.h | ||
| btree_inet.c | ||
| btree_int2.c | ||
| btree_int4.c | ||
| btree_int8.c | ||
| btree_interval.c | ||
| btree_macaddr8.c | ||
| btree_macaddr.c | ||
| btree_numeric.c | ||
| btree_oid.c | ||
| btree_text.c | ||
| btree_time.c | ||
| btree_ts.c | ||
| btree_utils_num.c | ||
| btree_utils_num.h | ||
| btree_utils_var.c | ||
| btree_utils_var.h | ||
| btree_uuid.c | ||
| Makefile | ||