Materialized view vs regular view decision in PostgreSQL - Performance Comparison

Time Complexity: Materialized view vs regular view decision

O(n) for regular view queries, O(1) for materialized view queries

Understanding Time Complexity

When choosing between a materialized view and a regular view, it's important to understand how their execution time changes as data grows.

We want to know how query speed behaves with each option as the database gets bigger.

Scenario Under Consideration

Analyze the time complexity of querying a regular view versus a materialized view.

-- Regular view definition
CREATE VIEW sales_summary AS
SELECT product_id, SUM(quantity) AS total_quantity
FROM sales
GROUP BY product_id;

-- Materialized view definition
CREATE MATERIALIZED VIEW sales_summary_mat AS
SELECT product_id, SUM(quantity) AS total_quantity
FROM sales
GROUP BY product_id;

-- Querying the views
SELECT * FROM sales_summary;
SELECT * FROM sales_summary_mat;

The regular view runs the aggregation each time it is queried, while the materialized view stores the result and returns it directly.

Identify Repeating Operations

Look at what happens when you query each view.

• Primary operation: Scanning and grouping the entire sales table.
• How many times: For the regular view, this happens every query; for the materialized view, it happens only when refreshed.

How Execution Grows With Input

As the sales table grows, the time to compute the aggregation grows too.

Input Size (n rows)	Regular View Query Time	Materialized View Query Time
10	Small, quick scan	Almost instant (precomputed)
1000	Longer scan and group	Still almost instant
1000000	Much longer scan and group	Still almost instant

Pattern observation: Regular view query time grows roughly with data size; materialized view query time stays nearly constant.

Final Time Complexity

Time Complexity: O(n) for regular view queries, O(1) for materialized view queries

This means regular views take longer as data grows, while materialized views return results quickly because they store precomputed data.

Common Mistake

[X] Wrong: "Materialized views always speed up queries without any extra cost."

[OK] Correct: Materialized views need to be refreshed to update data, which can take time and resources, so they are not always the best choice for frequently changing data.

Interview Connect

Understanding when to use materialized views versus regular views shows you can balance query speed and data freshness, a key skill in real database work.

Self-Check

"What if the materialized view is refreshed automatically after every insert? How would that affect the time complexity of queries and updates?"

Practice

1. Which statement best describes a regular view in PostgreSQL?

easy

A. It stores data physically and requires manual refresh.

B. It cannot be used in SELECT statements.

C. It runs the underlying query every time it is accessed.

D. It automatically updates data without running queries.

Solution

1. Step 1: Understand what a regular view does

   A regular view is a saved SQL query that runs fresh every time you use it.

2. Step 2: Compare with other options

   Storing data physically and requiring manual refresh describes a materialized view; saying it cannot be used in SELECT statements is false because views can be queried directly; automatically updating data without running queries is incorrect for regular views.

3. Final Answer:

   It runs the underlying query every time it is accessed. -> Option C

4. Quick Check:

   Regular view runs query each time [OK]

Hint: Regular views always run queries fresh on access [OK]

Common Mistakes:

• Confusing materialized views with regular views
• Thinking views store data physically
• Believing views auto-refresh data

2. Which of the following is the correct syntax to create a materialized view in PostgreSQL?

easy

A. CREATE MATERIALIZED VIEW my_mat_view AS SELECT * FROM sales;

B. CREATE VIEW my_view AS SELECT * FROM sales;

C. CREATE TABLE my_mat_view AS SELECT * FROM sales;

D. CREATE TEMP VIEW my_mat_view AS SELECT * FROM sales;

Solution

1. Step 1: Identify syntax for materialized view

   The correct syntax uses CREATE MATERIALIZED VIEW followed by the view name and query.

2. Step 2: Eliminate incorrect options

   CREATE VIEW my_view AS SELECT * FROM sales; creates a regular view, CREATE TABLE my_mat_view AS SELECT * FROM sales; creates a table, CREATE TEMP VIEW my_mat_view AS SELECT * FROM sales; creates a temporary view, not materialized.

3. Final Answer:

   CREATE MATERIALIZED VIEW my_mat_view AS SELECT * FROM sales; -> Option A

4. Quick Check:

   Materialized view syntax includes 'MATERIALIZED' keyword [OK]

Hint: Materialized views use 'CREATE MATERIALIZED VIEW' syntax [OK]

Common Mistakes:

• Using CREATE VIEW instead of CREATE MATERIALIZED VIEW
• Confusing tables with materialized views
• Using TEMP keyword incorrectly

3. Given a materialized view created as:
CREATE MATERIALIZED VIEW sales_summary AS SELECT region, SUM(amount) AS total FROM sales GROUP BY region;
What will be the result of:
SELECT * FROM sales_summary;
immediately after creation?

medium

A. The aggregated total sales per region based on current data.

B. An error because materialized views need manual refresh first.

C. Empty result set because no data is stored yet.

D. The detailed sales rows without aggregation.

Solution

1. Step 1: Understand materialized view creation behavior

   When created, a materialized view stores the query result immediately.

2. Step 2: Determine output of SELECT from materialized view

   It returns the aggregated totals per region as per the query at creation time.

3. Final Answer:

   The aggregated total sales per region based on current data. -> Option A

4. Quick Check:

   Materialized view stores query result on creation [OK]

Hint: Materialized views store data on creation, so SELECT returns stored results [OK]

Common Mistakes:

• Thinking materialized views are empty until refreshed
• Expecting detailed rows instead of aggregated results
• Assuming errors occur without manual refresh

4. You created a materialized view but notice it shows outdated data after the underlying table changes. What is the best way to fix this?

medium

A. Use SELECT * FROM materialized_view to refresh automatically.

B. Drop and recreate the materialized view every time.

C. Restart the PostgreSQL server to refresh views.

D. Run REFRESH MATERIALIZED VIEW to update the data.

Solution

1. Step 1: Identify how to update materialized view data

   Materialized views do not auto-update; REFRESH MATERIALIZED VIEW command updates stored data.

2. Step 2: Evaluate other options

   Dropping and recreating the materialized view every time is inefficient, using SELECT * FROM materialized_view does not refresh it, restarting the PostgreSQL server is unrelated.

3. Final Answer:

   Run REFRESH MATERIALIZED VIEW to update the data. -> Option D

4. Quick Check:

   Use REFRESH MATERIALIZED VIEW to update data [OK]

Hint: Use REFRESH MATERIALIZED VIEW to update stored data [OK]

Common Mistakes:

• Expecting SELECT to refresh data automatically
• Dropping and recreating instead of refreshing
• Restarting server to fix view data

5. You have a large sales table updated hourly. You want fast reports that summarize sales by region but can tolerate data up to 1 hour old. Which is the best choice?

hard

A. Use a regular view to always get fresh data.

B. Use a materialized view refreshed every hour for faster queries.

C. Create a table with triggers to update summaries instantly.

D. Use a temporary view refreshed on each query.

Solution

1. Step 1: Analyze requirements for speed and data freshness

   Reports need fast access and can accept data up to 1 hour old.

2. Step 2: Match options to requirements

   Materialized views store results and can be refreshed hourly, balancing speed and freshness. Regular views run slow on large data. Triggers add complexity. Temporary views do not persist.

3. Final Answer:

   Use a materialized view refreshed every hour for faster queries. -> Option B

4. Quick Check:

   Materialized view + hourly refresh = best for speed and acceptable freshness [OK]

Hint: Materialized views with scheduled refresh balance speed and freshness [OK]

Common Mistakes:

• Choosing regular views despite slow queries
• Using triggers unnecessarily complex
• Confusing temporary views with materialized views