Query optimization with EXPLAIN in Supabase - Time & Space Complexity

Time Complexity: Query optimization with EXPLAIN

O(n)

Understanding Time Complexity

When we run database queries, some take longer than others. Using EXPLAIN helps us see how the database plans to run a query.

We want to understand how the time to run a query grows as the data size grows.

Scenario Under Consideration

Analyze the time complexity of a SELECT query with EXPLAIN.

const { data, error } = await supabase.rpc('explain_query', {
  query: 'EXPLAIN SELECT * FROM users WHERE age > 30'
});

This runs EXPLAIN on a query to see how the database will execute it.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: The database scans or indexes rows to find matches.
• How many times: Depends on number of rows in the table scanned or indexed.

How Execution Grows With Input

As the number of rows grows, the database work grows too.

Input Size (n)	Approx. Api Calls/Operations
10	About 10 row checks
100	About 100 row checks
1000	About 1000 row checks

Pattern observation: The work grows roughly in direct proportion to the number of rows scanned.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows roughly in a straight line with the number of rows checked.

Common Mistake

[X] Wrong: "EXPLAIN makes the query run faster by itself."

[OK] Correct: EXPLAIN only shows the plan; it does not speed up the query execution.

Interview Connect

Understanding how query time grows helps you design better databases and write faster queries, a useful skill in many cloud roles.

Self-Check

"What if we add an index on the age column? How would the time complexity change?"

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