Query optimization with EXPLAIN in Supabase - Step-by-Step Execution

Process Flow - Query optimization with EXPLAIN

Write SQL Query

↓

Run EXPLAIN on Query

↓

Get Query Plan

↓

Analyze Steps

↓

Identify Bottlenecks

↓

Rewrite Query or Add Index

↓

Test Optimized Query

↓

Repeat if Needed

This flow shows how to use EXPLAIN to see how a query runs, find slow parts, and improve it step-by-step.

Execution Sample

Supabase

EXPLAIN SELECT * FROM users WHERE age > 30;

This command shows the query plan for selecting users older than 30.

Process Table

Step	Action	Query Plan Detail	Result/Output
1	Parse SQL	Check syntax and structure	Valid query
2	Generate Plan	Scan 'users' table with filter age > 30	Seq Scan or Index Scan
3	Estimate Cost	Calculate rows and cost	Cost: 10..1000 rows: 50
4	Output Plan	Show plan tree	Seq Scan on users Filter: age > 30
5	Analyze Plan	Look for full table scan or missing index	Full scan detected, consider index
6	Add Index	Create index on age column	Index created
7	Re-run EXPLAIN	Check new plan	Index Scan on users using age_idx
8	Compare Costs	New cost lower than before	Cost: 5..200 rows: 50
9	End	Optimization complete	Query runs faster with index

💡 Optimization ends after comparing costs and confirming improved query plan.

Status Tracker

Variable	Start	After Step 5	After Step 7	Final
Query Plan Type	Not generated	Seq Scan (full table scan)	Index Scan (using age_idx)	Index Scan (using age_idx)
Estimated Cost	N/A	10..1000	5..200	5..200
Rows Estimated	N/A	50	50	50
Index Present	No	No	Yes	Yes

Key Moments - 3 Insights

Why does EXPLAIN show a sequential scan before adding an index?

Because without an index, the database must check every row to find matches, as shown in step 4 of the execution_table.

How do we know the query got faster after optimization?

The estimated cost decreased from 10..1000 to 5..200 after adding the index, as seen in steps 3 and 8.

What does the 'Filter: age > 30' mean in the plan?

It means the database only keeps rows where age is greater than 30 during the scan, shown in step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what type of scan is used before adding the index?

A Index Scan

B Bitmap Scan

C Seq Scan

D No Scan

💡 Hint

Check Step 4 in the execution_table where the plan shows 'Seq Scan on users'.

At which step does the query plan change to use the index?

A Step 5

B Step 7

C Step 3

D Step 9

💡 Hint

Look at Step 7 in the execution_table where it says 'Index Scan on users using age_idx'.

If the index was not created, how would the estimated cost change?

A It would stay high like 10..1000

B It would become zero

C It would decrease to 5..200

D It would be unpredictable

💡 Hint

Refer to Step 3 and Step 8 in the execution_table comparing costs before and after index creation.

Concept Snapshot

Use EXPLAIN before running a query to see its plan.
Look for full table scans as a sign of slow queries.
Add indexes on columns used in filters to speed up scans.
Re-run EXPLAIN to confirm the plan uses the index.
Lower estimated cost means better performance.
Repeat until query is efficient.

Full Transcript

Query optimization with EXPLAIN involves running the EXPLAIN command on a SQL query to see how the database plans to execute it. The plan shows steps like scanning tables and filtering rows. Initially, without indexes, the database may do a full table scan, which is slow. By analyzing the plan, you can identify bottlenecks such as missing indexes. Adding an index on the filtered column helps the database use a faster index scan. Re-running EXPLAIN shows the improved plan with lower estimated cost, meaning the query will run faster. This process can be repeated to further optimize queries.

Practice

1. What is the main purpose of using EXPLAIN in Supabase queries?

easy

A. To execute the query faster automatically

B. To see how the database plans to run your query

C. To delete data from the database

D. To create new tables in the database

Solution

1. Step 1: Understand the role of EXPLAIN

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

2. Step 2: Differentiate EXPLAIN from other commands

   It does not execute or change data; it only provides information about query execution.

3. Final Answer:

   To see how the database plans to run your query -> Option B

4. Quick Check:

   EXPLAIN = query plan info [OK]

Hint: EXPLAIN shows query plans, not data changes [OK]

Common Mistakes:

• Thinking EXPLAIN runs the query faster
• Confusing EXPLAIN with data modification commands
• Assuming EXPLAIN creates or deletes tables

2. Which of the following is the correct syntax to get detailed execution info of a query in Supabase?

easy

A. EXPLAIN ANALYZE SELECT * FROM users;

B. EXPLAIN SELECT * FROM users;

C. ANALYZE EXPLAIN SELECT * FROM users;

D. SELECT EXPLAIN ANALYZE * FROM users;

Solution

1. Step 1: Recall the syntax for detailed query execution

   To get real execution details, use EXPLAIN ANALYZE before the query.

2. Step 2: Check each option's syntax

   EXPLAIN ANALYZE SELECT * FROM users; correctly places EXPLAIN ANALYZE before the SELECT statement; others are incorrect or invalid.

3. Final Answer:

   EXPLAIN ANALYZE SELECT * FROM users; -> Option A

4. Quick Check:

   EXPLAIN ANALYZE = detailed execution [OK]

Hint: Use EXPLAIN ANALYZE before SELECT for details [OK]

Common Mistakes:

• Swapping EXPLAIN and ANALYZE order
• Placing EXPLAIN inside SELECT
• Using ANALYZE without EXPLAIN

3. Given the EXPLAIN output shows a sequential scan on a large table, what is the likely effect on query performance?

medium

A. The query will be very fast because it uses an index

B. The query will fail due to missing indexes

C. The query will only scan a small part of the table

D. The query might be slow because it reads the whole table

Solution

1. Step 1: Understand sequential scan meaning

   A sequential scan reads every row in the table, which can be slow for large tables.

2. Step 2: Compare with index scan

   Index scans read only relevant rows, making queries faster; sequential scans do not use indexes.

3. Final Answer:

   The query might be slow because it reads the whole table -> Option D

4. Quick Check:

   Seq scan = full table read, slower [OK]

Hint: Seq scan reads all rows, slowing large queries [OK]

Common Mistakes:

• Assuming sequential scan uses indexes
• Thinking sequential scan reads only part of table
• Confusing failure with slow performance

4. You run EXPLAIN ANALYZE SELECT * FROM orders WHERE customer_id = 123; but notice the query is slow. What is a likely cause and fix?

medium

A. No index on customer_id; add an index on that column

B. The query syntax is wrong; rewrite the SELECT statement

C. The database is offline; restart the server

D. The table orders does not exist; create it first

Solution

1. Step 1: Analyze slow query cause

   Slow queries filtering by a column often mean missing indexes on that column.

2. Step 2: Suggest fix based on EXPLAIN ANALYZE

   Adding an index on customer_id helps the database find rows faster, improving speed.

3. Final Answer:

   No index on customer_id; add an index on that column -> Option A

4. Quick Check:

   Missing index = slow filter; add index [OK]

Hint: Slow filtered query? Check indexes on filter columns [OK]

Common Mistakes:

• Assuming syntax error causes slowness
• Restarting server without checking query plan
• Thinking missing table causes slow query

5. You want to optimize a complex query joining two large tables. The EXPLAIN ANALYZE shows nested loops causing slow performance. What is the best approach to improve it?

hard

A. Increase the database server's CPU without changing the query

B. Remove all indexes to force sequential scans

C. Add indexes on join columns and rewrite query to use explicit JOIN syntax

D. Split the query into multiple smaller queries without joins

Solution

1. Step 1: Understand nested loops impact

   Nested loops join can be slow on large tables without proper indexes on join columns.

2. Step 2: Apply optimization techniques

   Adding indexes on join columns helps the database find matching rows faster. Using explicit JOIN syntax clarifies the query for optimization.

3. Final Answer:

   Add indexes on join columns and rewrite query to use explicit JOIN syntax -> Option C

4. Quick Check:

   Indexes + clear JOIN = faster joins [OK]

Hint: Index join columns and use explicit JOIN for speed [OK]

Common Mistakes:

• Removing indexes causing slower scans
• Splitting queries losing join benefits
• Relying only on hardware upgrades