EXPLAIN ANALYZE for actual execution in PostgreSQL - Step-by-Step Execution

Concept Flow - EXPLAIN ANALYZE for actual execution

Start Query

↓

Parse Query

↓

Plan Query

↓

Execute Query

↓

Collect Actual Stats

↓

Display Execution Plan with Stats

↓

End

The database parses and plans the query, executes it, collects real execution stats, and then shows the plan with actual timing and row counts.

Execution Sample

PostgreSQL

EXPLAIN ANALYZE SELECT * FROM employees WHERE department = 'Sales';

This command runs the query and shows the actual execution plan with timing and row counts.

Execution Table

Step	Action	Details	Result
1	Parse Query	Read and check syntax	Query parsed successfully
2	Plan Query	Create execution plan	Plan created: Seq Scan on employees
3	Execute Query	Run plan to fetch rows	Rows filtered by department='Sales'
4	Collect Stats	Measure time and rows	Actual time: 0.5 ms, Rows: 10
5	Display Plan	Show plan with actual stats	Seq Scan: actual time=0.5..0.7 ms, rows=10
6	End	Finish execution	Query complete

💡 Execution ends after query runs and stats are collected and displayed

Variable Tracker

Variable	Start	After Parse	After Plan	After Execute	After Stats	Final
Query Text	EXPLAIN ANALYZE SELECT * FROM employees WHERE department = 'Sales';	Parsed	Planned	Executed	Stats Collected	Displayed
Rows Returned	N/A	N/A	N/A	10	10	10
Execution Time (ms)	N/A	N/A	N/A	0.7	0.7	0.7

Key Moments - 3 Insights

Why does EXPLAIN ANALYZE take longer than just EXPLAIN?

Because EXPLAIN ANALYZE actually runs the query to collect real execution times and row counts, as shown in execution_table steps 3 and 4.

What does 'actual time=0.5..0.7 ms' mean in the output?

It shows the start and end time of the operation during execution, meaning the step began at 0.5 ms and finished at 0.7 ms, as seen in execution_table step 5.

Why are the number of rows important in EXPLAIN ANALYZE?

Because actual rows processed help verify if the plan matches real data, helping detect inefficiencies, as tracked in variable_tracker for 'Rows Returned'.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the query actually run and fetch rows?

A Step 3

B Step 2

C Step 5

D Step 1

💡 Hint

Check the 'Action' column for 'Execute Query' in execution_table row 3.

According to variable_tracker, what is the number of rows returned after execution?

A N/A

B 0

C 10

D 5

💡 Hint

Look at the 'Rows Returned' row under 'After Execute' and later columns.

If EXPLAIN ANALYZE did not collect actual stats, which step would be missing in execution_table?

A Step 6

B Step 4

C Step 2

D Step 1

💡 Hint

Step 4 is 'Collect Stats' which gathers real execution data.

Concept Snapshot

EXPLAIN ANALYZE runs a query and shows the actual execution plan.
It includes real timing and row counts.
Syntax: EXPLAIN ANALYZE <query>;
Useful to find slow parts and optimize queries.
Shows steps: parse, plan, execute, collect stats, display.
Helps compare estimated vs actual performance.

Full Transcript

EXPLAIN ANALYZE is a command in PostgreSQL that runs a query and shows the real execution plan with timing and row counts. The process starts by parsing the query to check syntax, then planning how to run it. Next, the query is executed, and actual statistics like time taken and rows processed are collected. Finally, the plan with these real stats is displayed to the user. This helps understand how the database runs the query and where it spends time. The execution table shows each step clearly, and the variable tracker follows key values like rows returned and execution time. Beginners often wonder why EXPLAIN ANALYZE takes longer than EXPLAIN alone — this is because it runs the query fully to gather real data. The actual time values show when each step started and ended. The number of rows processed is important to verify the plan's accuracy. This visual execution helps learners see the flow from query start to finish with real performance data.

Practice

1. What is the main purpose of using EXPLAIN ANALYZE in PostgreSQL?

easy

A. To only check the syntax of the SQL query without running it

B. To run the query and show the actual execution plan with timing details

C. To delete data from the database safely

D. To create a backup of the database

Solution

1. Step 1: Understand what EXPLAIN ANALYZE does

   It runs the SQL query and collects detailed information about how the database executes it, including timing and row counts.

2. Step 2: Compare with other options

   Options A, C, and D describe different actions unrelated to EXPLAIN ANALYZE's purpose.

3. Final Answer:

   To run the query and show the actual execution plan with timing details -> Option B

4. Quick Check:

   EXPLAIN ANALYZE = actual execution plan with timing [OK]

Hint: EXPLAIN ANALYZE runs query and shows real execution details [OK]

Common Mistakes:

• Thinking EXPLAIN ANALYZE only checks syntax
• Confusing it with backup or delete commands
• Assuming it does not run the query

2. Which of the following is the correct syntax to get the actual execution plan of a query SELECT * FROM users; using EXPLAIN ANALYZE?

easy

A. EXPLAIN SELECT * FROM users;

B. EXPLAIN RUN SELECT * FROM users;

C. EXPLAIN ANALYZE SELECT * FROM users;

D. ANALYZE EXPLAIN SELECT * FROM users;

Solution

1. Step 1: Recall the correct EXPLAIN ANALYZE syntax

   The correct syntax is to write EXPLAIN ANALYZE followed by the query to run and analyze.

2. Step 2: Check each option

   EXPLAIN SELECT * FROM users; misses ANALYZE, so it only shows estimated plan. ANALYZE EXPLAIN SELECT * FROM users; reverses keywords incorrectly. EXPLAIN RUN SELECT * FROM users; uses an invalid keyword RUN.

3. Final Answer:

   EXPLAIN ANALYZE SELECT * FROM users; -> Option C

4. Quick Check:

   EXPLAIN ANALYZE + query = correct syntax [OK]

Hint: EXPLAIN ANALYZE before query runs it and shows plan [OK]

Common Mistakes:

• Omitting ANALYZE keyword
• Swapping EXPLAIN and ANALYZE order
• Using invalid keywords like RUN

3. Given the query EXPLAIN ANALYZE SELECT * FROM orders WHERE order_id = 10;, which part of the output tells you how many rows were actually returned?

medium

A. The "Buffers" section

B. The "Estimated Rows" value in the output

C. The "Planning Time" value

D. The "Actual Rows" value in the output

Solution

1. Step 1: Understand EXPLAIN ANALYZE output fields

   "Actual Rows" shows the real number of rows returned by each step during execution.

2. Step 2: Differentiate from other fields

   "Estimated Rows" is the planner's guess before running. "Planning Time" is time spent planning. "Buffers" shows disk usage, not row count.

3. Final Answer:

   The "Actual Rows" value in the output -> Option D

4. Quick Check:

   Actual Rows = real returned rows [OK]

Hint: "Actual Rows" shows real returned rows, not estimates [OK]

Common Mistakes:

• Confusing estimated rows with actual rows
• Looking at planning time for row count
• Ignoring actual execution details

4. You run ANALYZE EXPLAIN SELECT * FROM products WHERE price > 100; but get an error: ERROR: syntax error at or near "EXPLAIN". What is the likely cause?

medium

A. You wrote ANALYZE before EXPLAIN

B. You forgot the semicolon at the end

C. You used EXPLAIN without ANALYZE

D. You ran the query without EXPLAIN

Solution

1. Step 1: Analyze the error message

   The error points to a syntax problem near "EXPLAIN" which suggests wrong keyword order.

2. Step 2: Check correct keyword order

   The correct order is EXPLAIN ANALYZE, not ANALYZE EXPLAIN. Writing ANALYZE first causes syntax error.

3. Final Answer:

   You wrote ANALYZE before EXPLAIN -> Option A

4. Quick Check:

   EXPLAIN must come before ANALYZE [OK]

Hint: EXPLAIN always comes before ANALYZE in syntax [OK]

Common Mistakes:

• Swapping EXPLAIN and ANALYZE keywords
• Missing semicolon (usually different error)
• Running query without EXPLAIN ANALYZE

5. You want to optimize a slow query joining customers and orders. Using EXPLAIN ANALYZE, you see a sequential scan on orders despite an index on customer_id. What should you check or do next?

hard

A. Check if statistics are outdated and run ANALYZE orders;

B. Drop the index on customer_id to force sequential scan

C. Rewrite the query without JOIN to avoid scans

D. Increase the database cache size to ignore indexes

Solution

1. Step 1: Understand why index might be ignored

   If statistics are outdated, the planner may wrongly choose a sequential scan instead of using the index.

2. Step 2: Use ANALYZE to update statistics

   Running ANALYZE orders; updates table statistics so planner can make better decisions.

3. Final Answer:

   Check if statistics are outdated and run ANALYZE orders; -> Option A

4. Quick Check:

   Update stats with ANALYZE to help planner use indexes [OK]

Hint: Run ANALYZE to update stats so planner uses indexes [OK]

Common Mistakes:

• Dropping useful indexes
• Ignoring statistics update
• Trying to avoid JOINs instead of fixing plan