Query optimization with EXPLAIN in Supabase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the EXPLAIN command in SQL?

EXPLAIN shows how the database plans to execute a query. It helps understand the steps and resources used, so you can find ways to make the query faster.

beginner

What does a sequential scan mean in an EXPLAIN output?

A sequential scan means the database reads the whole table row by row. It can be slow for big tables and might mean missing indexes.

intermediate

How can indexes improve query performance according to EXPLAIN?

Indexes let the database find rows faster without scanning the whole table. EXPLAIN shows index scans when indexes are used, which usually means faster queries.

intermediate

What does the 'cost' value in EXPLAIN output represent?

The cost is a number estimating how much work the database needs to do to run the query. Lower cost means less work and usually faster queries.

beginner

Why is it important to analyze EXPLAIN output before optimizing queries?

Analyzing EXPLAIN helps you see where the query spends time and resources. This guides you to add indexes or rewrite queries to make them faster.

What does EXPLAIN show in Supabase SQL?

A How the database plans to run a query

B The exact time a query took to run

C The number of rows returned by a query

D The syntax errors in a query

EXPLAIN shows the query plan, not execution time or errors.

If EXPLAIN shows a sequential scan on a large table, what might help improve performance?

A Running the query multiple times

B Adding an index on the searched column

C Increasing the database storage size

D Deleting rows from the table

Indexes help avoid full table scans and speed up queries.

What does a lower cost value in EXPLAIN indicate?

A More CPU used

B More rows returned

C Less work needed to run the query

D Longer query time

Lower cost means the database expects less work to execute the query.

Which EXPLAIN output indicates the use of an index?

A Sort

B Seq Scan

C Hash Join

D Index Scan

Index Scan means the query uses an index to find rows.

Why should you use EXPLAIN before changing a query?

A To understand how the query runs and find bottlenecks

B To check spelling mistakes

C To count the number of tables

D To backup the database

EXPLAIN helps identify slow parts of a query to optimize.

Explain how EXPLAIN helps optimize SQL queries in Supabase.

Think about what EXPLAIN reveals about query steps and resource use.

Describe what a sequential scan is and why it might slow down a query.

Imagine reading a whole book to find one word versus using the index.

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