Indexing materialized views in PostgreSQL - Mini Project: Build & Apply

Indexing Materialized Views in PostgreSQL

📖 Scenario: You work as a database assistant for a bookstore. The store wants to speed up queries that summarize sales data by author. To do this, you will create a materialized view that stores total sales per author and then add an index to make searching faster.

🎯 Goal: Create a materialized view named author_sales_summary that shows total sales per author from the sales table. Then add an index on the author column of this materialized view to speed up queries.

📋 What You'll Learn

Create a materialized view called author_sales_summary with columns author and total_sales.

The materialized view should sum the amount column grouped by author from the sales table.

Create an index named idx_author_sales_summary_author on the author column of the materialized view.

Use standard PostgreSQL syntax.

💡 Why This Matters

🌍 Real World

Materialized views help speed up complex queries by storing precomputed results. Indexing them makes lookups even faster.

💼 Career

Database administrators and developers often use materialized views and indexes to optimize reporting and analytics in real-world applications.

1

Create the materialized view

Write a SQL statement to create a materialized view named author_sales_summary. It should select author and the sum of amount as total_sales from the sales table, grouped by author.

PostgreSQL

-- Your code here to create the materialized view author_sales_summary

Hint

Use CREATE MATERIALIZED VIEW view_name AS SELECT ... GROUP BY ... syntax.

2

Add an index name variable

Create a variable called index_name and set it to the string 'idx_author_sales_summary_author'. This will hold the name of the index you will create.

PostgreSQL

CREATE MATERIALIZED VIEW author_sales_summary AS
SELECT author, SUM(amount) AS total_sales
FROM sales
GROUP BY author;

-- Your code here to create the index_name variable

Hint

Use \set index_name 'index_name_here' to define a psql variable.

3

Create the index on the materialized view

Write a SQL statement to create an index named idx_author_sales_summary_author on the author column of the author_sales_summary materialized view.

PostgreSQL

CREATE MATERIALIZED VIEW author_sales_summary AS
SELECT author, SUM(amount) AS total_sales
FROM sales
GROUP BY author;

\set index_name 'idx_author_sales_summary_author'

-- Your code here to create the index on author column

Hint

Use CREATE INDEX index_name ON view_name(column_name);

4

Refresh the materialized view

Write a SQL statement to refresh the author_sales_summary materialized view so it contains the latest data.

PostgreSQL

CREATE MATERIALIZED VIEW author_sales_summary AS
SELECT author, SUM(amount) AS total_sales
FROM sales
GROUP BY author;

\set index_name 'idx_author_sales_summary_author'

CREATE INDEX idx_author_sales_summary_author ON author_sales_summary(author);

-- Your code here to refresh the materialized view

Hint

Use REFRESH MATERIALIZED VIEW view_name; to update the data.

Practice

1. What is the main purpose of creating an index on a materialized view in PostgreSQL?

easy

A. To speed up query performance on the materialized view

B. To automatically refresh the materialized view

C. To store the materialized view data physically

D. To prevent the materialized view from being updated

Solution

1. Step 1: Understand what an index does

   An index helps the database find data faster by creating a quick lookup structure.

2. Step 2: Apply this to materialized views

   Since materialized views store query results physically, indexing them speeds up queries on that stored data.

3. Final Answer:

   To speed up query performance on the materialized view -> Option A

4. Quick Check:

   Indexing = Faster queries [OK]

Hint: Indexes speed up data retrieval on stored results [OK]

Common Mistakes:

• Thinking indexes refresh the view automatically
• Confusing storage with indexing
• Believing indexes prevent updates

2. Which of the following is the correct syntax to create an index on a materialized view named sales_summary on column region?

easy

A. CREATE INDEX idx_region ON TABLE sales_summary(region);

B. CREATE INDEX idx_region ON MATERIALIZED VIEW sales_summary(region);

C. CREATE INDEX idx_region ON sales_summary(region);

D. CREATE INDEX idx_region ON VIEW sales_summary(region);

Solution

1. Step 1: Recall index creation syntax

   Indexes are created with CREATE INDEX index_name ON table_name(column); syntax.

2. Step 2: Apply to materialized views

   Materialized views behave like tables for indexing, so no extra keywords like MATERIALIZED VIEW or VIEW are used.

3. Final Answer:

   CREATE INDEX idx_region ON sales_summary(region); -> Option C

4. Quick Check:

   Index syntax = CREATE INDEX name ON table(column) [OK]

Hint: Use table syntax for materialized views when creating indexes [OK]

Common Mistakes:

• Adding MATERIALIZED VIEW keyword in index creation
• Using VIEW keyword instead of table name
• Incorrect syntax with TABLE keyword

3. Given a materialized view mv_orders with an index on order_date, what will be the output of this query?

SELECT order_date FROM mv_orders WHERE order_date = '2023-01-01';

Assuming the materialized view is refreshed and contains data for that date.

medium

A. Returns all rows with order_date '2023-01-01' quickly using the index

B. Returns an error because indexes cannot be used on materialized views

C. Returns no rows because materialized views do not store data

D. Returns all rows but ignores the index, causing slow performance

Solution

1. Step 1: Understand index usage on materialized views

   Indexes on materialized views speed up queries by quickly locating matching rows.

2. Step 2: Analyze the query behavior

   The query filters by order_date, which is indexed, so it returns matching rows efficiently.

3. Final Answer:

   Returns all rows with order_date '2023-01-01' quickly using the index -> Option A

4. Quick Check:

   Indexed query = fast matching rows [OK]

Hint: Indexed columns speed up matching queries on materialized views [OK]

Common Mistakes:

• Thinking indexes don't work on materialized views
• Assuming materialized views are empty without refresh
• Believing query ignores indexes always

4. You created an index on a materialized view but notice queries are still slow. What is the most likely cause?

medium

A. Indexes do not work on materialized views in PostgreSQL

B. The materialized view has not been refreshed after data changes

C. The index was created on a non-existent column

D. Materialized views cannot have indexes on date columns

Solution

1. Step 1: Understand materialized view refresh

   Materialized views store data physically but need manual refresh to update data and indexes.

2. Step 2: Connect refresh to query speed

   If not refreshed, the view and its index are outdated, causing slow or incorrect query results.

3. Final Answer:

   The materialized view has not been refreshed after data changes -> Option B

4. Quick Check:

   Refresh needed for updated data and index [OK]

Hint: Always refresh materialized views after data changes [OK]

Common Mistakes:

• Believing indexes don't work on materialized views
• Creating index on wrong column silently
• Thinking date columns can't be indexed

5. You have a materialized view mv_sales refreshed daily. You want to speed up queries filtering by customer_id and sale_date. Which is the best indexing strategy?

hard

A. Do not create any index; rely on sequential scan

B. Create separate indexes on customer_id and sale_date individually

C. Create an index only on sale_date because it is a date column

D. Create a single composite index on (customer_id, sale_date)

Solution

1. Step 1: Understand composite vs single indexes

   A composite index on multiple columns speeds up queries filtering by both columns together.

2. Step 2: Apply to query filtering by customer_id and sale_date

   Since queries filter on both columns, a composite index is more efficient than separate indexes.

3. Final Answer:

   Create a single composite index on (customer_id, sale_date) -> Option D

4. Quick Check:

   Composite index = faster multi-column filters [OK]

Hint: Use composite index for multi-column filtering queries [OK]

Common Mistakes:

• Creating separate indexes causing less efficient queries
• Indexing only one column when filtering by two
• Skipping indexes and relying on slow scans