diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-15 16:10:48 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-15 16:10:58 -0500 |
commit | 29d29d652f0be47dc42fa9d667dee5b8e1baa18a (patch) | |
tree | b0a4290d860803427ff955aa075acdfbc77aa110 /src/backend/access/gist/gistproc.c | |
parent | 46cf3c72c36fef8c623b4b97d8720321d8ad7507 (diff) | |
download | postgresql-29d29d652f0be47dc42fa9d667dee5b8e1baa18a.tar.gz |
Fix fuzzy thinking about amcanmulticol versus amcaninclude.
These flags should be independent: in particular an index AM should
be able to say that it supports include columns without necessarily
supporting multiple key columns. The included-columns patch got
this wrong, possibly aided by the fact that it didn't bother to
update the documentation.
While here, clarify some text about amcanreturn, which was a little
vague about what should happen when amcanreturn reports that only
some of the index columns are returnable.
Noted while reviewing the SP-GiST included-columns patch, which
quite incorrectly (and unsafely) changed SP-GiST to claim
amcanmulticol = true as a workaround for this bug.
Backpatch to v11 where included columns were introduced.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions