aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorAlexander Korotkov <akorotkov@postgresql.org>2019-03-10 11:36:47 +0300
committerAlexander Korotkov <akorotkov@postgresql.org>2019-03-10 11:37:17 +0300
commitf2e403803fe6deb8cff59ea09dff42c6163b2110 (patch)
tree1c3afef6e11f6498002b88219d9644e71bb5972d /src/backend/access/gist/gistvacuum.c
parenta0b762626884b3b949c2703abb1c4b42fbbdfdc6 (diff)
downloadpostgresql-f2e403803fe6deb8cff59ea09dff42c6163b2110.tar.gz
postgresql-f2e403803fe6deb8cff59ea09dff42c6163b2110.zip
Support for INCLUDE attributes in GiST indexes
Similarly to B-tree, GiST index access method gets support of INCLUDE attributes. These attributes aren't used for tree navigation and aren't present in non-leaf pages. But they are present in leaf pages and can be fetched during index-only scan. The point of having INCLUDE attributes in GiST indexes is slightly different from the point of having them in B-tree. The main point of INCLUDE attributes in B-tree is to define UNIQUE constraint over part of attributes enabled for index-only scan. In GiST the main point of INCLUDE attributes is to use index-only scan for attributes, whose data types don't have GiST opclasses. Discussion: https://postgr.es/m/73A1A452-AD5F-40D4-BD61-978622FF75C1%40yandex-team.ru Author: Andrey Borodin, with small changes by me Reviewed-by: Andreas Karlsson
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions