A bitmap records table-row or table-page locations matching an index condition so PostgreSQL can retrieve matching data in bulk. section 4.5.2
Bitmap access proceeds in two phases:
- Bitmap Index Scan finds matching index entries and records their table locations without immediately fetching rows. section 4.5.2
- Bitmap Heap Scan visits the referenced table rows, reducing repeated table lookups during multi-value searches. section 4.5.2
- When matches consume more memory, PostgreSQL may record whole table pages instead of individual rows, producing lossy information. section 4.5.2
Retrieving several indexed values
A query using champion_title IN (...) produces a Bitmap Index Scan followed by a Bitmap Heap Scan. The plan reports five rows and four exact heap blocks, showing how matching locations are collected before table access. section 4.5.2
SELECT username, score, level FROM game.player_stats WHERE champion_title = 'Naval Warlord';
Open the indexed lookup example, then inspect the related execution plan to see bitmap access in runnable SQL. section 4.5.2

