Condense a supplied database execution-plan discussion into a short evidence-based reading. Select this for query operators and row flow, not general benchmark reporting.

Identify the query or supplied label, database version, and whether the plan is estimated or executed. Keep operators that explain cost, actual timing, row-estimate errors, repeated loops, sorting, spills, and filtering. Retain exact table, index, and predicate names. Distinguish planner cost units from elapsed time and per-loop values from totals.

Collapse uninformative plan scaffolding and repeated commentary. Preserve cache state, parameter values, and measurement conditions that limit the result. State a suspected bottleneck as a suspicion unless the evidence establishes it. Keep proposed changes separate from measured outcomes.

Output Query, Evidence, and Interpretation lines, with a proposed next check only if supplied. Do not execute SQL, recommend a destructive change, invent an index, or claim that a suggested rewrite improved performance without a measured comparison.