# Chapter 6: The Intended Job Before beginning the iterative revision, I am restating the purpose and "North Star" of this chapter to ensure a unified voice. ## What is this chapter for? This chapter is the **"Field Guide to Performance."** It transition the reader from "Query Algebra" (How it works) to "Database Physics" (Why it's stuck). It provides the diagnostic tools and mental models to identify resource bottlenecks in a live server. ## What should the reader understand by the end? - **The Diagnostic Split**: Performance is the ratio of **Execution** (The Sweat) to **Waiting** (The Sigh). - **Wait Categories**: Differentiate between **I/O** (Disk), **Lock** (Integrity), and **LWLock** (Memory Safety). - **Relationship of Tools**: How `EXPLAIN (ANALYZE, BUFFERS)` and `pg_stat_activity` work together. - **Systematic Reasoning**: How to identify the "Shape" of a workload (CPU, IO, or Wait-bound) and move toward a fix. ## What MUST stay? - The **Elephant Cafe** metaphor (Warming Racks, Frozen Pantries, Narrow Bridges). - The **Wait Mode Heuristics** (100% CPU = Sweat; Low CPU/Slow Work = Sigh). - The **Diagnostic Trio Guide** in 6.5. ## What can move, shrink, or disappear? - The granular detail of `SLRU` or `RelationMap` mechanisms (can be merged). - The distinction between internal parallel coordination latches (can be generalized under `LWLocks`). - Any technical jargon that doesn't map to a physical cafe metaphor. ## The Revision North Star > "If the reader sees an entry in `pg_stat_activity`, they should be able to physically visualize where that elephant is standing in the Cafe and what is holding them up."