Materialized view vs regular view decision in PostgreSQL - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

When to use a materialized view instead of a regular view?

You have a large table with millions of rows that rarely changes. You want to speed up complex queries that aggregate data from this table. Which option best explains when to use a materialized view instead of a regular view?

A Use a materialized view when you want faster query results by storing the query output physically, but you must refresh it manually or on schedule.

B Use a materialized view when you want the query to always show the latest data without any delay.

C Use a materialized view when you want to avoid storing any data and always compute results on the fly.

D Use a materialized view only if the underlying tables are updated every second.

💡 Hint

Think about whether the data is stored or computed each time you query.

A materialized view stores the query result physically, which speeds up queries but requires manual or scheduled refresh to update data. A regular view computes data on demand and always shows the latest data but can be slower.

❓ query_result

intermediate

Output difference between materialized view and regular view

Given a table sales with columns id, amount, and sale_date, you create a regular view and a materialized view that calculate total sales per day. If a new sale is inserted after creating both views, what will be the output of querying each view?

PostgreSQL

CREATE VIEW daily_sales_view AS SELECT sale_date, SUM(amount) AS total FROM sales GROUP BY sale_date;

CREATE MATERIALIZED VIEW daily_sales_matview AS SELECT sale_date, SUM(amount) AS total FROM sales GROUP BY sale_date;

-- After inserting a new sale:
INSERT INTO sales VALUES (101, 500, '2024-06-15');

-- Query both views:
SELECT * FROM daily_sales_view WHERE sale_date = '2024-06-15';
SELECT * FROM daily_sales_matview WHERE sale_date = '2024-06-15';

A Neither view shows the new sale until the materialized view is refreshed.

B Both views show the new sale total immediately after insertion.

C The regular view shows the new sale total including the inserted row; the materialized view does not show the new sale until refreshed.

D The materialized view shows the new sale total immediately; the regular view does not.

💡 Hint

Remember how materialized views store data versus regular views.

Regular views compute results on demand, so they reflect the latest data immediately. Materialized views store results physically and require manual refresh to update.

❓ optimization

advanced

Optimizing query performance with materialized views

You have a complex query joining multiple large tables and aggregating data. The query runs slowly when executed frequently. Which approach will best improve performance using materialized views?

A Avoid using views and run the complex query directly every time.

B Create a materialized view with the complex query and schedule regular refreshes during low-traffic hours.

C Create a regular view with the complex query and index the underlying tables heavily.

D Create a materialized view but never refresh it after creation.

💡 Hint

Think about balancing query speed and data freshness.

Materialized views store query results physically, speeding up queries. Scheduling refreshes during low-traffic times keeps data reasonably fresh without slowing down users.

🔧 Debug

advanced

Why does querying a materialized view show outdated data?

You created a materialized view from a table and query it multiple times. You notice the data does not reflect recent changes in the base table. What is the most likely cause?

A The query on the materialized view is missing a WHERE clause.

B The base table is locked and cannot update the materialized view automatically.

C Materialized views always show outdated data by design.

D The materialized view has not been refreshed since the base table was updated.

💡 Hint

Consider how materialized views update their data.

Materialized views do not update automatically when base tables change. They require manual or scheduled refresh to show current data.

🧠 Conceptual

expert

Choosing between materialized view and regular view for real-time analytics

You are designing a dashboard that shows real-time analytics updated every second. The underlying data changes frequently. Which is the best choice and why?

A Use a regular view because it always shows the latest data without needing refresh.

B Use a materialized view because it stores data and speeds up queries even if data is slightly outdated.

C Use a materialized view and refresh it every second to keep data real-time.

D Use neither; export data to a flat file for faster access.

💡 Hint

Think about data freshness and update frequency.

Regular views compute data on demand, so they always reflect the latest changes, which is essential for real-time analytics. Materialized views require refresh and may lag behind.