You have a materialized view mv_sales_summary that aggregates sales data daily. You want to refresh it every hour without blocking users querying it. Which approach is best?

hard📝 Application Q8 of 15

PostgreSQL - Views and Materialized Views

You have a materialized view mv_sales_summary that aggregates sales data daily. You want to refresh it every hour without blocking users querying it. Which approach is best?

ADrop and recreate the materialized view every hour

BUse <code>REFRESH MATERIALIZED VIEW mv_sales_summary;</code> without CONCURRENTLY

CUse <code>REFRESH MATERIALIZED VIEW CONCURRENTLY mv_sales_summary;</code> scheduled hourly

DManually update the materialized view data with INSERT statements

Step-by-Step Solution

Solution:

Step 1: Identify requirement for non-blocking refresh
Users must query while refresh runs, so no blocking allowed.
Step 2: Choose best refresh method
REFRESH MATERIALIZED VIEW CONCURRENTLY allows refresh without blocking queries.
Final Answer:
Use REFRESH MATERIALIZED VIEW CONCURRENTLY mv_sales_summary; scheduled hourly -> Option C
Quick Check:
Non-blocking refresh = CONCURRENTLY option [OK]

Quick Trick: Schedule CONCURRENTLY refresh for non-blocking updates [OK]

Common Mistakes:

Dropping and recreating wastes resources and blocks queries
Using refresh without CONCURRENTLY blocks users
Trying manual inserts to update materialized view

Master "Views and Materialized Views" in PostgreSQL

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

You have a materialized view mv_sales_summary that aggregates sales data daily. You want to refresh it every hour without blocking users querying it. Which approach is best?

Step 1: Identify requirement for non-blocking refresh

Step 2: Choose best refresh method

Final Answer:

Quick Check:

Want More Practice?