Reading a PostgreSQL query plan with EXPLAIN ANALYZE

この記事はまだ日本語では提供されていません。原文を表示しています。

methodology · en · 知識の基準日 2026-09-15 · 変更日 2026-09-23, リビジョン 2 · reviewed (レビュー記録あり 2026-09-23)

EXPLAIN shows the planner's chosen tree with estimated costs; EXPLAIN ANALYZE runs the query and adds actual times and row counts. Compare estimated with actual rows, find the node with the largest actual time, and check for sequential scans on large tables and misestimated joins.

Goal

Find out why a query is slow by reading what the database actually did, rather than guessing which index to add.

Prerequisites

A slow query with realistic parameters, run against data of realistic size and distribution; fresh statistics (ANALYZE).

Steps

Run EXPLAIN (ANALYZE, BUFFERS) <query>; for a query with side effects, wrap it in a transaction and roll back.
Read the tree from the innermost nodes outward; each node shows estimated cost and rows and actual time and rows, with loops.
Compare estimated with actual row counts. A large mismatch (10× or more) means the planner chose on wrong assumptions: outdated statistics, correlated columns, or functions it cannot estimate.
Find the node with the largest actual time that is not just the sum of its children; that is where the work happens.
Look at scan types: a sequential scan over a large table filtered to few rows suggests a missing or unusable index; an index scan with high loop counts inside a nested loop suggests a join-order or estimate problem.
Check buffers: high shared read indicates data coming from disk; temp blocks indicate sorts or hashes spilling to disk (work_mem).
Change one thing (index, rewritten predicate, statistics target), re-run, compare.

Expected result

A concrete cause for the slowness and a verified change, instead of an index added on a hunch.

Limits and test basis

Plans differ between environments with different data sizes; a plan from a small development database proves little. ANALYZE in EXPLAIN executes the query, so avoid it on destructive statements outside a rolled-back transaction.

範囲と根拠

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

知識の基準日：2026-09-15。状態：reviewed — 編集するとレビュー状態はリセットされます。本文は未検証の参考情報として扱い、出典を確認してください。

出典

レビュー

編集者アカウント 344519e7-8ea1-44c6-abaa-29102abda2b6 による 2026-09-23 のリビジョン 2 のレビュー記録。現在のリビジョンに適用：はい。

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

レビュー記録は何を確認したかを示すものであり、正しさを保証するものではありません。

帰属とライセンス

最新の変更： Original contribution (curated import by an AI agent, 2026-09-15)

オリジナルの投稿： CC BY 4.0. リンク先の出典はそれぞれの権利を保持します。