Database indexes in Supabase - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main benefit of a database index?

Imagine you have a large table with millions of rows. You want to find rows quickly based on a column value. What does adding an index on that column do?

A It speeds up data retrieval by allowing the database to find rows faster.

B It compresses the data to save storage space.

C It automatically backs up the table data regularly.

D It encrypts the column data for security.

💡 Hint

Think about how a book's index helps you find a topic quickly.

An index creates a quick lookup structure that helps the database find rows without scanning the entire table.

❓ service_behavior

intermediate

What happens when you query a table without an index on the searched column?

You run a query filtering by a column that has no index. What is the expected behavior?

A The database caches the query results for future use.

B The database instantly returns results using a hidden index.

C The query fails with an error about missing indexes.

D The database scans every row in the table to find matches, which is slower.

💡 Hint

Without a map or index, how do you find a word in a dictionary?

Without an index, the database must check each row one by one, which takes more time.

❓ Configuration

advanced

Which SQL command creates a unique index on the 'email' column in a Supabase PostgreSQL table named 'users'?

Choose the correct SQL statement to create a unique index on the 'email' column.

A CREATE UNIQUE INDEX idx_users_email ON users(email);

B CREATE INDEX UNIQUE idx_users_email ON users(email);

C CREATE UNIQUE KEY idx_users_email ON users(email);

D CREATE INDEX idx_users_email UNIQUE ON users(email);

💡 Hint

Remember the correct order of keywords in PostgreSQL for unique indexes.

The correct syntax is CREATE UNIQUE INDEX index_name ON table(column);

❓ security

advanced

What is a potential security risk of indexing sensitive columns like passwords?

Why should you avoid creating indexes on sensitive data columns such as passwords?

A Indexes slow down the database, causing denial of service.

B Indexes store data in plain text, which can expose sensitive information if accessed.

C Indexes prevent data encryption on those columns.

D Indexes automatically share data with third-party services.

💡 Hint

Think about where index data is stored and who can access it.

Indexes can store copies of column data in plain text, so indexing sensitive data risks exposure if the index is accessed.

❓ Architecture

expert

In a Supabase project, you want to optimize read performance for a table with frequent writes and reads. Which indexing strategy balances performance best?

Given a table with many inserts and updates, but also many read queries filtering by 'status' and 'created_at', which indexing approach is best?

A Avoid indexes entirely to keep write speed high, accepting slower reads.

B Create separate indexes on 'status' and 'created_at' columns to maximize read speed at any cost.

C Create a composite index on (status, created_at) to speed up filtered reads while minimizing write overhead.

D Create a full-text index on all columns to cover all query types.

💡 Hint

Think about how composite indexes help with multi-column queries and write costs.

A composite index on the queried columns improves read speed for those filters and reduces the number of indexes to update on writes, balancing performance.

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