Materialized view vs regular view decision in PostgreSQL - Quick Revision & Key Differences

Recall & Review

beginner

What is a regular view in PostgreSQL?

A regular view is a saved SQL query that acts like a virtual table. It does not store data itself but shows data from underlying tables when queried.

beginner

What is a materialized view in PostgreSQL?

A materialized view stores the result of a query physically. It saves data on disk and must be refreshed to update its content.

intermediate

When should you choose a materialized view over a regular view?

Choose a materialized view when the query is complex and slow, and the data does not need to be real-time. It improves performance by storing precomputed results.

intermediate

What is a downside of using materialized views?

Materialized views require manual or scheduled refresh to update data, so they can show outdated information if not refreshed regularly.

beginner

How does a regular view handle data updates?

A regular view always shows the latest data from the underlying tables because it runs the query fresh each time it is accessed.

Which of the following stores data physically in PostgreSQL?

A Materialized view

B Regular view

C Temporary table

D Index

Materialized views store query results physically, unlike regular views which are virtual.

What must you do to update data in a materialized view?

A Run REFRESH MATERIALIZED VIEW

B Update the underlying tables only

C Drop and recreate the view

D Nothing, it updates automatically

Materialized views require a manual refresh command to update their stored data.

Which view type always shows the most current data?

A Neither

B Materialized view

C Both

D Regular view

Regular views run the query each time, so they always show current data.

When is it better to use a regular view instead of a materialized view?

A When you want to store data physically

B When query is very slow

C When data changes frequently and must be current

D When you want to save disk space

Regular views are better for frequently changing data that needs to be up-to-date.

What is a main benefit of materialized views?

A No need to refresh

B Faster query performance for complex queries

C Always up-to-date data

D No disk space used

Materialized views improve performance by storing precomputed results.

Explain the key differences between a materialized view and a regular view in PostgreSQL.

Think about storage and data freshness.

Describe scenarios when you would choose a materialized view over a regular view.

Consider performance and data update frequency.

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