Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitc6221db

Browse files
committed
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.
1 parent631e031 commitc6221db

File tree

2 files changed

+16
-18
lines changed

2 files changed

+16
-18
lines changed

‎doc/TODO

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated:Thu Apr 2100:09:27 EDT 2005
5+
Last updated:Thu Apr 2111:20:13 EDT 2005
66

77
The most recent version of this document can be viewed at the PostgreSQL web
88
site, http://www.PostgreSQL.org.
@@ -300,14 +300,13 @@ Indexes
300300

301301
* Allow non-bitmap indexes to be combined by creating bitmaps in memory
302302

303-
Bitmap indexes index single columns that can be combined with other bitmap
304-
indexes to dynamically create a composite index to match a specific query.
305-
Each index is a bitmap, and the bitmaps are bitwise AND'ed or OR'ed to be
306-
combined. They can index by tid or can be lossy requiring a scan of the
307-
heap page to find matching rows, or perhaps use a mixed solution where
308-
tids are recorded for pages with only a few matches and per-page bitmaps
309-
are used for more dense pages. Another idea is to use a 32-bit bitmap
310-
for every page and set a bit based on the item number mod(32).
303+
This feature allows separate indexes to be ANDed or ORed together. This
304+
is particularly useful for data warehousing applications that need to
305+
query the database in an many permutations. This feature scans an index
306+
and creates an in-memory bitmap, and allows that bitmap to be combined
307+
with other bitmap created in a similar way. The bitmap can either index
308+
all TIDs, or be lossy, meaning it records just page numbers and each
309+
page tuple has to be checked for validity in a separate pass.
311310

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

‎doc/src/FAQ/TODO.html

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
99
<h1><aname="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
11-
Last updated: Thu Apr 2100:09:27 EDT 2005
11+
Last updated: Thu Apr 2111:20:13 EDT 2005
1212
</p>
1313
<p>The most recent version of this document can be viewed at the PostgreSQL web<br/>
1414
site,<ahref="http://www.PostgreSQL.org">http://www.PostgreSQL.org</a>.
@@ -277,14 +277,13 @@ <h1><a name="section_6">Indexes</a></h1>
277277
before accessing the heap rows.
278278
</p>
279279
</li><li>Allow non-bitmap indexes to be combined by creating bitmaps in memory
280-
<p> Bitmap indexes index single columns that can be combined with other bitmap
281-
indexes to dynamically create a composite index to match a specific query.
282-
Each index is a bitmap, and the bitmaps are bitwise AND'ed or OR'ed to be
283-
combined. They can index by tid or can be lossy requiring a scan of the
284-
heap page to find matching rows, or perhaps use a mixed solution where
285-
tids are recorded for pages with only a few matches and per-page bitmaps
286-
are used for more dense pages. Another idea is to use a 32-bit bitmap
287-
for every page and set a bit based on the item number mod(32).
280+
<p> This feature allows separate indexes to be ANDed or ORed together. This
281+
is particularly useful for data warehousing applications that need to
282+
query the database in an many permutations. This feature scans an index
283+
and creates an in-memory bitmap, and allows that bitmap to be combined
284+
with other bitmap created in a similar way. The bitmap can either index
285+
all TIDs, or be lossy, meaning it records just page numbers and each
286+
page tuple has to be checked for validity in a separate pass.
288287
</p>
289288
</li><li>Allow the creation of on-disk bitmap indexes which can be quickly
290289
combined with other bitmap indexes

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp