MVCC & visibilitysenior🔒 Pro concept

Visibility map & index-only scans

Simple terms

Every table page carries a bit meaning every row here is visible to everyone. That bit is what makes an index-only scan possible: the index already holds your answer, and the bit is permission to trust it without opening the table. VACUUM sets the bit. Any write clears it. So an index-only scan is a privilege, not a property, leave a long transaction open, VACUUM can't set the bits, and Heap Fetches climbs in EXPLAIN while your fast plan quietly goes back to touching the heap.

You might be asked

What is the visibility map, what is the 'Heap Fetches' line in an Index Only Scan, and why can a long-running transaction silently turn a fast index-only scan back into one that visits the heap?

TopicHeap storage / VACUUM / planner-executor
PostgreSQL14, 15, 16, 17, 18
Tools usedpg_visibility (pg_visibility_map_summary), EXPLAIN (ANALYZE, BUFFERS), pg_class.relallvisible, VACUUM, a long-running concurrent session, source navigation @REL_17_10
Last reviewed2026-06-19

Pro concept

Full answer and evidence depth sit behind Pro

You have the question and a plain-English lead. Pro unlocks the short answer, what the docs say, what the code does, the labeled lab evidence or reproduction protocol, how to use it under pressure, and the references.

ProFull answer + evidence depth

Unlock the full breakdown for Visibility map & index-only scans

You have the interview question and a plain-English lead. Pro opens the short answer, the manual walkthrough, the source decode, and a 159-line evidence section that states whether it is raw output, a captured run summary, or a protocol to run yourself, plus how to use it under pressure.
  • How you'd answer it, the full senior-level short answer
  • What the docs say, the manual's actual wording, with the citations
  • What the code does, the mechanism decoded from PostgreSQL's own source at a pinned tag
  • Proof from a real run, labeled as raw output, a captured run summary, or a run-it-yourself protocol
  • Using it under pressure, the situation, the call you'd make, what goes wrong, and what people get wrong
  • Version notes, what changed across PostgreSQL releases
  • 4 interviewer follow-ups for this concept

Card required. Cancel before day 7 and you are not charged.

Compare plans

How this was verified

The open teaser is the question and a plain-English lead. The short answer, the manual walkthrough, the source decode, the lab evidence, and how to use it under pressure unlock with Pro. Evidence is labeled as raw output, a captured run summary, or a run-it-yourself protocol.

Connected

Where this concept connects

How this concept links across the library, the interview questions that test it, its plain-English glossary definition, and the guided pathways it belongs to. Open the full map to explore further.

Open in the interactive map →