You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So if I understand this correctly, the hnsw index type does not support index-only and we want to implement it? Ref:
The index type must support index-only scans. B-tree indexes always do. GiST and SP-GiST indexes support index-only scans for some operator classes but not others. Other index types have no support. The underlying requirement is that the index must physically store, or else be able to reconstruct, the original data value for each index entry. As a counterexample, GIN indexes cannot support index-only scans because each index entry typically holds only part of the original data value.
Access methods API descriptions: https://www.postgresql.org/docs/9.5/catalog-pg-am.html
I think as a first step we can implement amcanreturn and then support INCLUDE later. Effectively if we only query the column cover by the index then we would still be doing an index-only scan.
Note: this is quite an involved issue. It will require understanding of the index storage format and structures on postgres blocks.
Relevant links:
CREATE INDEX
docs(search forINCLUDE
)The text was updated successfully, but these errors were encountered: