aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2005-04-21 15:20:39 +0000
committerBruce Momjian <bruce@momjian.us>2005-04-21 15:20:39 +0000
commitc6221db3c0f7049b804391d59aeadcfbd1f51800 (patch)
tree1fab0cbedc7bb46dd955dd290b72093c5a2c1b98 /src/backend/tcop/postgres.c
parent631e03145f823f758b12f7a3ed17409cf303f9dd (diff)
downloadpostgresql-c6221db3c0f7049b804391d59aeadcfbd1f51800.tar.gz
postgresql-c6221db3c0f7049b804391d59aeadcfbd1f51800.zip
Updated text for bitmaps:
< Bitmap indexes index single columns that can be combined with other bitmap < indexes to dynamically create a composite index to match a specific query. < Each index is a bitmap, and the bitmaps are bitwise AND'ed or OR'ed to be < combined. They can index by tid or can be lossy requiring a scan of the < heap page to find matching rows, or perhaps use a mixed solution where < tids are recorded for pages with only a few matches and per-page bitmaps < are used for more dense pages. Another idea is to use a 32-bit bitmap < for every page and set a bit based on the item number mod(32). > This feature allows separate indexes to be ANDed or ORed together. This > is particularly useful for data warehousing applications that need to > query the database in an many permutations. This feature scans an index > and creates an in-memory bitmap, and allows that bitmap to be combined > with other bitmap created in a similar way. The bitmap can either index > all TIDs, or be lossy, meaning it records just page numbers and each > page tuple has to be checked for validity in a separate pass.
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions