Changing one number from 32 to 34 made a Postgres query 6,000× faster. Here's exactly why.
A step-by-step walk through the Postgres planner: how join_collapse_limit splits your joins before useless joins are removed, why the safe values have holes, what to ship, and what Postgres 16+ changes.
