Skip to content

Commit 056d7e3

Browse files
committed
Add bitmap info:
< heap page to find matching rows. > 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).
1 parent 9a633cb commit 056d7e3

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

doc/TODO

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ TODO list for PostgreSQL
66
Bracketed items "[]" have more detail.
77

88
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
9-
Last updated: Tue Nov 9 11:50:52 EST 2004
9+
Last updated: Tue Nov 9 21:48:31 EST 2004
1010

1111
The most recent version of this document can be viewed at the PostgreSQL web
1212
site, http://www.PostgreSQL.org.
@@ -256,7 +256,10 @@ Indexes
256256
indexes to dynamically create a composite index to match a specific query.
257257
Each index is a bitmap, and the bitmaps are bitwise AND'ed or OR'ed to be
258258
combined. They can index by tid or can be lossy requiring a scan of the
259-
heap page to find matching rows.
259+
heap page to find matching rows, or perhaps use a mixed solution where
260+
tids are recorded for pages with only a few matches and per-page bitmaps
261+
are used for more dense pages. Another idea is to use a 32-bit bitmap
262+
for every page and set a bit based on the item number mod(32).
260263

261264
* Allow the creation of on-disk bitmap indexes which can be quickly
262265
combined with other bitmap indexes

0 commit comments

Comments
 (0)