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:48 -0500 |
| commit | 7c89246d0bb233be7d6670f0a8f024e99423e8cc (patch) | |
| tree | 00ddaaebb2baba37d1de8d053425a005a422bd4d /src/backend/commands/prepare.c | |
| parent | 0e0e71abdcaeb8a3887094de078b77cb35bd03ba (diff) | |
| download | postgresql-7c89246d0bb233be7d6670f0a8f024e99423e8cc.tar.gz postgresql-7c89246d0bb233be7d6670f0a8f024e99423e8cc.zip | |
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/commands/prepare.c')
0 files changed, 0 insertions, 0 deletions