EXPLAIN ANALYZE is the standard tool for understanding how PostgreSQL runs a query. It shows the chosen plan, estimated and actual row counts, and execution time. For most engineers, it is the first stop when a query is slow.

It is also frequently misread. A query plan can look clean in EXPLAIN ANALYZE and still be slow in production. A rewritten query can show a much lower cost in development and behave identically when deployed. The output is not wrong — but it answers a narrower question than most readers assume.

This article walks through five common ways EXPLAIN ANALYZE is misinterpreted, and the additional tools and flags that fill in the gaps.

Pitfall #1: Treating "Cost" as a Time Estimate

The first column most readers look at is cost .…