Database indexes in Supabase - Step-by-Step Execution

Process Flow - Database indexes

Start Query

↓

Check for Index

Yes / No?↓

Use Index

↓

Return Results

↓

End

When a query runs, the database checks if an index exists for the search. If yes, it uses the index to find data fast. If no, it scans the whole table, which is slower.

Execution Sample

Supabase

CREATE INDEX idx_user_email ON users(email);

SELECT * FROM users WHERE email = '[e-mail]';

Create an index on the email column, then query users by email using the index for faster lookup.

Process Table

Step	Action	Index Exists?	Query Method	Result
1	Start query to find user by email	N/A	N/A	Query initiated
2	Check if index on email exists	Yes	Use Index	Index used to find matching rows
3	Retrieve matching rows using index	Yes	Use Index	Rows found quickly
4	Return results to client	Yes	Use Index	Results returned
5	End query	N/A	N/A	Query complete

💡 Query ends after using index to quickly find matching rows instead of scanning whole table

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
index_exists	undefined	true	true	true
query_method	undefined	use index	use index	use index
rows_found	0	0	5	5

Key Moments - 2 Insights

Why does the database check for an index before searching?

The database checks for an index (see Step 2 in execution_table) to decide if it can find data quickly. Using an index avoids scanning the whole table, making queries faster.

What happens if there is no index on the searched column?

If no index exists, the database does a full table scan (not shown here). This means it looks at every row, which is slower than using an index.

Visual Quiz - 3 Questions

Look at the execution_table, what is the query method used at Step 3?

A Full table scan

B No method

C Use index

D Cache lookup

💡 Hint

Check the 'Query Method' column at Step 3 in the execution_table

At which step does the database confirm the index exists?

A Step 2

B Step 4

C Step 1

D Step 5

💡 Hint

Look at the 'Index Exists?' column in the execution_table

If the index did not exist, how would the 'query_method' variable change after Step 2?

A It would be 'use index'

B It would be 'full table scan'

C It would be 'no method'

D It would be 'cache lookup'

💡 Hint

Refer to variable_tracker for 'query_method' and think about what happens if no index is found

Concept Snapshot

Database indexes speed up data searches.
Create an index on columns you query often.
Database checks for index before searching.
If index exists, it uses it to find rows fast.
Without index, it scans the whole table slowly.

Full Transcript

When you run a query to find data, the database first checks if there is an index on the column you are searching. If an index exists, it uses that index to quickly find matching rows instead of scanning the entire table. This makes queries much faster. For example, creating an index on the email column lets the database find users by email quickly. If no index exists, the database must scan every row, which takes more time. This process is shown step-by-step in the execution table and variable tracker.

Practice

1. What is the main purpose of creating a database index in Supabase?

easy

A. To speed up data searches and queries

B. To store more data in the database

C. To backup the database automatically

D. To encrypt the data for security

Solution

1. Step 1: Understand what an index does

   An index creates a quick lookup structure to find data faster.

2. Step 2: Compare options with index purpose

   Only speeding up searches matches the index function.

3. Final Answer:

   To speed up data searches and queries -> Option A

4. Quick Check:

   Index = Faster search [OK]

Hint: Indexes speed up searches, not storage or security [OK]

Common Mistakes:

• Thinking indexes store more data
• Confusing indexes with backups
• Assuming indexes encrypt data

2. Which of the following is the correct SQL syntax to create an index on the column email in a Supabase table named users?

easy

A. CREATE INDEX email ON users;

B. INDEX CREATE users.email;

C. CREATE INDEX ON users (email);

D. CREATE users INDEX email;

Solution

1. Step 1: Recall correct SQL index syntax

   The standard syntax is: CREATE INDEX index_name ON table_name (column_name); but index_name is optional.

2. Step 2: Match syntax with options

   CREATE INDEX ON users (email); uses correct syntax without specifying index name, which is allowed.

3. Final Answer:

   CREATE INDEX ON users (email); -> Option C

4. Quick Check:

   CREATE INDEX ON table (column) [OK]

Hint: Use CREATE INDEX ON table (column) for indexes [OK]

Common Mistakes:

• Placing column before table incorrectly
• Using wrong keyword order
• Omitting ON keyword

3. Given the table orders with an index on customer_id, what will be the effect of this query?

SELECT * FROM orders WHERE customer_id = 123;

medium

A. The query will return no results because indexes filter data

B. The query will ignore the index and scan the whole table

C. The query will fail due to missing index

D. The query will run faster by using the index on customer_id

Solution

1. Step 1: Understand index usage in queries

   Indexes help the database find matching rows quickly when filtering by indexed columns.

2. Step 2: Analyze the query filter

   The query filters by customer_id, which has an index, so the index will be used.

3. Final Answer:

   The query will run faster by using the index on customer_id -> Option D

4. Quick Check:

   Indexed column filter = faster query [OK]

Hint: Queries filtering indexed columns run faster [OK]

Common Mistakes:

• Thinking index causes query failure
• Assuming index filters out data
• Believing index is ignored automatically

4. You created multiple indexes on a Supabase table, but now data insertions are very slow. What is the most likely cause?

medium

A. Too many indexes slow down data changes

B. Indexes cause data loss during insert

C. Indexes prevent data from being inserted

D. Indexes automatically delete old data

Solution

1. Step 1: Recall how indexes affect data changes

   Each index must be updated when data changes, so many indexes slow inserts and updates.

2. Step 2: Match symptoms with cause

   Slow insertions match the effect of too many indexes.

3. Final Answer:

   Too many indexes slow down data changes -> Option A

4. Quick Check:

   Many indexes = slower inserts [OK]

Hint: More indexes = slower writes, fewer indexes = faster writes [OK]

Common Mistakes:

• Thinking indexes cause data loss
• Assuming indexes block inserts
• Believing indexes delete data automatically

5. You want to optimize a Supabase table products that is frequently searched by category and price. Which index strategy is best to improve query speed without slowing inserts too much?

hard

A. Create no indexes to keep inserts fast

B. Create a composite index on (category, price)

C. Create an index only on price

D. Create separate indexes on category and price

Solution

1. Step 1: Understand composite vs separate indexes

   A composite index on (category, price) helps queries filtering both columns efficiently.

2. Step 2: Consider insert performance

   One composite index is faster to update than two separate indexes, balancing speed and insert cost.

3. Step 3: Evaluate options

   Create a composite index on (category, price) optimizes queries on both columns with minimal insert slowdown.

4. Final Answer:

   Create a composite index on (category, price) -> Option B

5. Quick Check:

   Composite index = faster multi-column queries [OK]

Hint: Use composite indexes for multi-column searches [OK]

Common Mistakes:

• Creating too many separate indexes
• Indexing only one column when both are searched
• Avoiding indexes and hurting query speed