EXPLAIN - Insights: Lossy Bitmaps
A bitmap heap scan can use bitmap blocks that either directly point to the rows needed (Exact Heap Blocks), or, roughly speaking, point in the general direction of the rows (Lossy Heap Blocks). The exact mechanism is more efficient overall, but requires more memory. When
work_mem limits do not permit using exact bitmaps, Postgres may switch to the less efficient lossy ones instead. Lossy bitmaps require a recheck step for each row. If possible, though, increasing work_mem until the scan uses mostly Exact Heap Blocks should improve performance.
work_mem for this query.
Couldn't find what you were looking for or want to talk about something specific?
Start a conversation with us →