EXPLAIN ANALYZE for actual execution in PostgreSQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does EXPLAIN ANALYZE do in PostgreSQL?

EXPLAIN ANALYZE runs a query and shows the actual steps PostgreSQL took to execute it, including time spent on each step and the number of rows processed.

beginner

Why is EXPLAIN ANALYZE useful compared to just EXPLAIN?

Unlike EXPLAIN which only shows the planned steps, EXPLAIN ANALYZE actually runs the query and shows real execution times and row counts, helping find slow parts.

intermediate

What kind of information does EXPLAIN ANALYZE output include?

• Execution time for each step
• Number of rows processed
• Actual vs estimated rows
• Cost estimates

intermediate

How can EXPLAIN ANALYZE help improve query performance?

By showing which steps take the most time or process more rows than expected, it helps identify bottlenecks and guides changes like adding indexes or rewriting queries.

beginner

Does EXPLAIN ANALYZE modify data when running a query?

No, it runs the query normally, so if the query changes data (like INSERT or UPDATE), those changes will happen.

Use it carefully with data-changing queries.

What does EXPLAIN ANALYZE show that EXPLAIN does not?

A Syntax errors in the query

B Only the query plan without execution

C Actual execution time and row counts

D Database schema details

EXPLAIN ANALYZE runs the query and shows real execution details, unlike EXPLAIN which only shows the planned steps.

Which of these is NOT included in EXPLAIN ANALYZE output?

A Estimated cost of query steps

B User permissions for the query

C Number of rows processed

D Actual time spent on each step

User permissions are not shown by EXPLAIN ANALYZE. It focuses on query execution details.

If a query modifies data, what happens when you run it with EXPLAIN ANALYZE?

A Only a simulation is done without execution

B The query runs but data is not changed

C The query is blocked from running

D The data changes are applied as usual

EXPLAIN ANALYZE runs the query normally, so data changes happen if the query modifies data.

How can EXPLAIN ANALYZE help you improve a slow query?

A By showing which steps take the most time

B By automatically fixing the query

C By deleting unnecessary data

D By increasing server memory

It helps identify slow parts of the query so you can optimize them.

Which command would you use to see the actual execution plan of a query in PostgreSQL?

A EXPLAIN ANALYZE SELECT * FROM table;

B SHOW PLAN SELECT * FROM table;

C DESCRIBE SELECT * FROM table;

D RUN PLAN SELECT * FROM table;

EXPLAIN ANALYZE runs the query and shows the actual execution plan.

Explain in your own words what EXPLAIN ANALYZE does and why it is useful.

Think about how seeing real times helps improve queries.

Describe the difference between EXPLAIN and EXPLAIN ANALYZE.

One just plans, the other runs and measures.

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