Plan Lenspostgres EXPLAIN, rendered

Your query's plan is a blueprint. Read it like one.

Paste the JSON from EXPLAIN (ANALYZE, BUFFERS, FORMAT JSON). This renders the execution tree, marks which node actually burned the time, and redlines every place the planner's row estimate was badly wrong — the single most common root cause of a slow plan.

explain output

Nothing sent anywhere — this all runs in your browser.

SHEETquery plan

SCALEn/a

REV—

DRAWNon paste

execution tree

cool — little of the total time

warm — a meaningful share of the time

hot — where most of the time actually went

red circle — planner's row estimate was off by 10x or more