Planning & executionsenior🔒 Pro concept

Parallel query: the Gather node, and planned vs launched workers

Simple terms

For a big scan Postgres can hand pieces of the work to helper processes and collect the results at a Gather node. How many helpers? It decides from the size of the table being scanned, not from how busy the machine is right now. That gap is why EXPLAIN shows two numbers, workers planned and workers launched. When they don't match, the planner asked for help that wasn't there, the server's worker slots were already taken, and your query ran with fewer hands than its cost assumed.

You might be asked

Explain how a parallel sequential scan actually runs. Where do the workers come from, who decides how many, what is the difference between 'Workers Planned' and 'Workers Launched', and what does the leader do while the workers run?

TopicParallel query: the Gather node, how worker count is chosen, planned vs launched, and leader participation
PostgreSQL9.6-17 (parallel query since 9.6; measured on 17.10)
Tools usedDocker pgi17 (PostgreSQL 17.10), EXPLAIN (ANALYZE, VERBOSE), source @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 Parallel query: the Gather node, and planned vs launched workers

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

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.