Concurrency & lockingstaff🔒 Pro concept

Multixacts (shared row locks)

Simple terms

A row has exactly one slot to record who is locking or deleting it. One transaction, one slot, no problem. Now a second transaction locks the same row for sharing. Two lockers, one slot. Postgres gets out of it by minting a separate id that stands for the whole group and storing that instead, so the slot now holds a pointer to a list rather than a transaction. That list lives in its own structure on disk, with its own wraparound clock to keep an eye on.

You might be asked

What is a multixact (MultiXactId), when does PostgreSQL create one, and how does it change the meaning of a tuple's t_xmax? Why do multixacts have their own wraparound horizon separate from transaction IDs?

TopicRow locking / tuple header / wraparound
PostgreSQL14, 15, 16, 17, 18
Tools usedpageinspect (heap_page_items, get_raw_page), pg_get_multixact_members(), mxid_age(), pg_current_xact_id(), two concurrent psql sessions, 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 Multixacts (shared row locks)

You have the interview question and a plain-English lead. Pro opens the short answer, the manual walkthrough, the source decode, and a 76-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 →