Core concepts for reading plan trees, understanding cost estimation, and diagnosing join strategies.
Explore section →
Understand Every
Query Execution Plan
Deep-dive guides for backend engineers, DBAs, and platform teams who need to diagnose slow queries, tune indexes, and extract real performance gains from PostgreSQL.
PostgreSQL's EXPLAIN and EXPLAIN ANALYZE commands expose exactly how the query planner
resolves your SQL — which access paths it chose, where time was spent, and where estimates diverged from reality.
Reading them accurately is the difference between guessing and knowing why a query is slow.
This site provides systematic diagnostic frameworks for every major execution plan pattern: sequential scan vs index
scan trade-offs, hash join memory spill detection, index-only scan validation, parallel worker allocation, filter
pushdown verification, and more. Each guide includes real annotated EXPLAIN ANALYZE output, remediation
steps, and the common pitfalls that lead engineers in the wrong direction.
Whether you're chasing a p95 latency regression, designing a covering index, or diagnosing why the planner ignores your carefully-crafted B-tree — the answers are in the plan. Let's learn to read them.
Explore the Guides
Systematic workflows for designing, optimizing, and maintaining indexes to eliminate I/O bottlenecks.
- B-Tree Index Optimization
- Covering Index Design
- Partial Index Implementation
- Specialized Index Types (GIN/GiST)
Frameworks for identifying bottlenecks, understanding parallel execution, and validating tuning outcomes.
- Filter Pushdown Mechanics
- Identifying Plan Bottlenecks
- Parallel Query Execution
- Sort and Hash Node Analysis