Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit c894e7e

Browse files
committed
Update bitmap index entries:
< * Allow the creation of bitmap indexes which can be quickly combined < with other bitmap indexes > * Allow non-bitmap indexes to be combined by creating bitmaps in memory 259,261c258,259 < combined. Such indexes could be more compact if there are few unique < value. Also, perhaps they can be lossy requiring a scan of the heap page < to find matching rows. > combined. They can index by tid or can be lossy requiring a scan of the > heap page to find matching rows. 263c261,262 < * Allow non-bitmap indexes to be combined > * Allow the creation of on-disk bitmap indexes which can be quickly > combined with other bitmap indexes 265,266c264 < Do lookups on non-bitmap indexes and create bitmaps in memory that can be < combined with other indexes. > Such indexes could be more compact if there are few unique value.
1 parent c874e77 commit c894e7e

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

doc/TODO

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

77
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
8-
Last updated: Wed Nov 3 22:57:53 EST 2004
8+
Last updated: Thu Nov 4 11:19:28 EST 2004
99

1010
The most recent version of this document can be viewed at the PostgreSQL web
1111
site, http://www.PostgreSQL.org.
@@ -250,20 +250,18 @@ Indexes
250250
order. Another method would be to sort heap ctids matching the index
251251
before accessing the heap rows.
252252

253-
* Allow the creation of bitmap indexes which can be quickly combined
254-
with other bitmap indexes
253+
* Allow non-bitmap indexes to be combined by creating bitmaps in memory
255254

256255
Bitmap indexes index single columns that can be combined with other bitmap
257256
indexes to dynamically create a composite index to match a specific query.
258257
Each index is a bitmap, and the bitmaps are bitwise AND'ed or OR'ed to be
259-
combined. Such indexes could be more compact if there are few unique
260-
value. Also, perhaps they can be lossy requiring a scan of the heap page
261-
to find matching rows.
258+
combined. They can index by tid or can be lossy requiring a scan of the
259+
heap page to find matching rows.
262260

263-
* Allow non-bitmap indexes to be combined
261+
* Allow the creation of on-disk bitmap indexes which can be quickly
262+
combined with other bitmap indexes
264263

265-
Do lookups on non-bitmap indexes and create bitmaps in memory that can be
266-
combined with other indexes.
264+
Such indexes could be more compact if there are few unique value.
267265

268266
* Allow use of indexes to search for NULLs
269267

0 commit comments

Comments
 (0)