Your question is Read PostgreSQL Plans to Find Slow Queries. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
Slow queries in PostgreSQL often come from bad join order, missing indexes, or row estimates that are far off. Reading the execution plan helps you pinpoint where time is spent instead of guessing.
You are asked to explain how you would read a PostgreSQL execution plan to determine why a query is slow. Walk through what you look for first, how you interpret row estimates versus actual rows, and how you identify expensive nodes such as sequential scans, sorts, hash joins, and nested loops.
Focus on practical plan-reading skills: what the key plan fields mean, how to spot the bottleneck, and how you would use EXPLAIN (ANALYZE, BUFFERS) to validate the diagnosis. Do not just define the terms — explain how they guide tuning decisions.