# Normalized Feedback: Chapter 6 - The Waiting Game This sheet collects all feedback from the Chapter 6 technical review for systematic prioritization. | Issue | Type | Location | Severity | Suggested Change | Judgment | | :--- | :--- | :--- | :--- | :--- | :--- | | **Missing frontmatter `---`** | Technical | 6.1.1, 6.1.2, 6.1.3, 6.3, 6.3.2, 6.3.3, 6.4, 6.4.1, 6.5 | **Critical** | Add `---` as the very first line of the file. | **Agree** (Mandatory fix) | | **Metaphor collision: "Waiter"** | Narrative | 6.1, 6.1.x | **Important** | Ensure "Waiter" = Application and "Chef/Staff" = Postgres workers. | **Agree** (Key "Great Good" alignment) | | **Missing 6.2.1 reference** | Structural | 6.2, 6.2.2 | **Important** | Create a missing section or renumber to bridge the gap. | **Agree** (Broken links) | | **Administrative IO Over-granularity** | Structural | 6.2.3, 6.2.4 | **Important** | Merge into `6.2.3 - The Infrastructure Ledgers`. | **Agree** (Reduces friction) | | **Internal Management Over-granularity** | Structural | 6.3.2, 6.3.3 | **Important** | Merge into `6.3.2 - Microscopic Traffic (Latches)`. | **Agree** (Reduces friction) | | **`pg_stat_statements` tool missing** | Explanatory | 6.0 | **Important** | Add a "Top 10" query example for diagnosing workloads. | **Agree** (Critical tool) | | **Blocking query complexity** | Explanatory | 6.3 | **Important** | Breakdown the `pg_locks` logic; simplify for developers. | **Agree** | | **NULL wait_event meaning** | Technical | 6.1 | **Minor** | Define NULL as "Execution / Busy" status. | **Agree** | | **`statement_timeout` missing** | Technical | 6.1.1 | **Minor** | Add reference to the common "Egg Timer" setting. | **Agree** | | **Typo: "Scaventer"** | Readability | 6.2 | **Minor** | Correct to "Scavenger". | **Agree** | | **SLRU memory location** | Technical | 6.2.4 | **Minor** | Clarify that SLRUs are separate from `shared_buffers`. | **Agree** | | **"Diner vs Factory" Acronyms** | Narrative | 6.0 | **Minor** | Bind OLTP/OLAP more explicitly to the metaphors. | **Agree** | ## Grouped Revision Patterns ### 1. The Global "Staffing" Pattern Resolved by renaming all Postgres workers to "Chefs" or "Staff" ensuring "Waiter" is exclusively the application client. ### 2. The Infrastructure Mergers Several short sub-chapters provide too much friction. Merging them into thematic "Administrative" sections keeps the reader focused on high-value diagnostic tasks. ### 3. Syntax Hygiene The `---` delimiter is missing from the head of nearly half the sub-chapters. This must be a global find-and-replace Fix. ### 4. Tooling & SQL Clarity Moving from "Geometric models" to actual SQL (`pg_stat_statements`, `pg_locks`) needs to be smoother.