1.4 Planner: Which Path to Take
The article discusses the planner stage in PostgreSQL's query processing. It explains how the planner takes a Query tree and produces a PlannedStmt, determining the execution path based on cost estimates. The planner's decision-making process involves evaluating multiple candidates for execution strategies, focusing on efficiency rather than correctness.
- ▪The planner's role is to determine how to execute a query after the rewriter has processed it.
- ▪It evaluates different execution strategies based on estimated costs derived from statistics.
- ▪The planner consists of two layers: Path, which generates candidate routes, and Plan, which finalizes the chosen execution route.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3911251) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } JoongHyuk Shin Posted on May 29 1.4 Planner: Which Path to Take #postgres #database #internals #planner PostgreSQL Internals (14 Part Series) 1 1.1 Where Does a Query Go? 2 1.1.1 Life of a Query ... 10 more parts...
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).