EXPLAIN output reading in PostgreSQL - Mini Project: Build & Apply

Understanding EXPLAIN Output in PostgreSQL

📖 Scenario: You are working as a junior database analyst. Your manager wants you to understand how PostgreSQL executes queries to help optimize them. You will learn to read the output of the EXPLAIN command, which shows the query plan.

🎯 Goal: Build a simple table, run a query, and use EXPLAIN to read and understand the query plan output.

📋 What You'll Learn

Create a table named employees with columns id (integer) and name (text).

Insert three specific rows into the employees table.

Write a SELECT query to get the employee with id = 2.

Use EXPLAIN to get the query plan for the SELECT query.

💡 Why This Matters

🌍 Real World

Understanding query plans helps database users and developers optimize queries for faster performance.

💼 Career

Database administrators and developers often use EXPLAIN to troubleshoot slow queries and improve database efficiency.

1

Create the employees table

Create a table called employees with two columns: id as integer and name as text.

PostgreSQL

-- Create the employees table with id and name columns
-- Your code here

Hint

Use CREATE TABLE employees (id INTEGER, name TEXT); to create the table.

2

Insert data into employees

Insert these three rows into the employees table: (1, 'Alice'), (2, 'Bob'), and (3, 'Charlie').

PostgreSQL

CREATE TABLE employees (id INTEGER, name TEXT);
-- Insert three rows into employees
-- Your code here

Hint

Use INSERT INTO employees (id, name) VALUES (1, 'Alice'), (2, 'Bob'), (3, 'Charlie');

3

Write a SELECT query to find employee with id = 2

Write a SELECT query to get all columns from employees where id = 2.

PostgreSQL

CREATE TABLE employees (id INTEGER, name TEXT);
INSERT INTO employees (id, name) VALUES (1, 'Alice'), (2, 'Bob'), (3, 'Charlie');
-- Write SELECT query to get employee with id = 2
-- Your code here

Hint

Use SELECT * FROM employees WHERE id = 2; to get the employee with id 2.

4

Use EXPLAIN to read the query plan

Add EXPLAIN before the SELECT query to see how PostgreSQL plans to execute it.

PostgreSQL

CREATE TABLE employees (id INTEGER, name TEXT);
INSERT INTO employees (id, name) VALUES (1, 'Alice'), (2, 'Bob'), (3, 'Charlie');
-- Use EXPLAIN before the SELECT query
-- Your code here

Hint

Use EXPLAIN SELECT * FROM employees WHERE id = 2; to see the query plan.

Practice

1. What does the EXPLAIN command in PostgreSQL primarily show?

easy

A. How PostgreSQL plans to execute a query

B. The exact data returned by the query

C. The syntax errors in the query

D. The database schema structure

Solution

1. Step 1: Understand the purpose of EXPLAIN

   EXPLAIN shows the query plan, which is how PostgreSQL intends to run the query.

2. Step 2: Differentiate from other commands

   It does not show actual data or errors, only the plan.

3. Final Answer:

   How PostgreSQL plans to execute a query -> Option A

4. Quick Check:

   EXPLAIN = query plan [OK]

Hint: EXPLAIN = query plan, not data or errors [OK]

Common Mistakes:

• Thinking EXPLAIN shows query results
• Confusing EXPLAIN with syntax error checks
• Assuming EXPLAIN shows database schema

2. Which of the following is the correct syntax to get the query plan for SELECT * FROM users; in PostgreSQL?

easy

A. EXPLAIN SELECT * FROM users;

B. EXPLAIN ANALYZE users SELECT *;

C. EXPLAIN FROM users SELECT *;

D. ANALYZE EXPLAIN SELECT * FROM users;

Solution

1. Step 1: Recall correct EXPLAIN syntax

   The correct syntax is EXPLAIN followed by the query.

2. Step 2: Check each option

   EXPLAIN SELECT * FROM users; matches the correct syntax. Others mix keywords incorrectly.

3. Final Answer:

   EXPLAIN SELECT * FROM users; -> Option A

4. Quick Check:

   EXPLAIN + query = correct syntax [OK]

Hint: EXPLAIN always precedes the query [OK]

Common Mistakes:

• Placing ANALYZE before EXPLAIN
• Using FROM before SELECT incorrectly
• Mixing keywords in wrong order

3. Given the EXPLAIN output below for SELECT * FROM orders WHERE customer_id = 5;, what does the line Index Scan using idx_customer_id on orders indicate?

medium

A. PostgreSQL is scanning the entire orders table

B. PostgreSQL is using an index to find matching rows

C. PostgreSQL is performing a sequential scan

D. PostgreSQL is creating a new index during query

Solution

1. Step 1: Understand 'Index Scan' meaning

   An Index Scan means PostgreSQL uses an index to quickly find rows matching the condition.

2. Step 2: Compare with other scan types

   Sequential scan means scanning all rows, which is not the case here.

3. Final Answer:

   PostgreSQL is using an index to find matching rows -> Option B

4. Quick Check:

   Index Scan = use index [OK]

Hint: 'Index Scan' means index used, not full table scan [OK]

Common Mistakes:

• Confusing Index Scan with Sequential Scan
• Thinking index is created during query
• Assuming full table scan always happens

4. You run EXPLAIN ANALYZE SELECT * FROM products WHERE price > 100; but get an error saying "relation 'products' does not exist." What is the likely cause?

medium

A. EXPLAIN ANALYZE cannot be used with WHERE clauses

B. The query syntax is incorrect for EXPLAIN ANALYZE

C. The table 'products' does not exist in the current database

D. You forgot to commit the transaction

Solution

1. Step 1: Analyze the error message

   The error says the table 'products' does not exist, meaning PostgreSQL cannot find it.

2. Step 2: Check other options

   EXPLAIN ANALYZE works with WHERE clauses and the syntax is correct. Committing transaction is unrelated.

3. Final Answer:

   The table 'products' does not exist in the current database -> Option C

4. Quick Check:

   Relation not found = missing table [OK]

Hint: Check table existence if 'relation does not exist' error appears [OK]

Common Mistakes:

• Assuming EXPLAIN ANALYZE disallows WHERE
• Blaming syntax when table is missing
• Thinking commit affects table visibility

5. You want to optimize a slow query. The EXPLAIN ANALYZE output shows a Seq Scan on a large table with a filter on a column. What is the best next step to improve performance?

hard

A. Drop the table and recreate it

B. Rewrite the query without the filter

C. Increase the work_mem setting

D. Create an index on the filtered column

Solution

1. Step 1: Understand Seq Scan impact

   A Seq Scan reads all rows, which is slow on large tables when filtering.

2. Step 2: Use index to speed filtering

   Creating an index on the filtered column lets PostgreSQL quickly find matching rows, avoiding full scan.

3. Final Answer:

   Create an index on the filtered column -> Option D

4. Quick Check:

   Seq Scan slow? Add index [OK]

Hint: Seq Scan slow? Add index on filter column [OK]

Common Mistakes:

• Removing filter instead of indexing
• Changing memory settings without indexing
• Dropping table unnecessarily