PostgreSQL - Views and Materialized Views
You have a materialized view mv_orders that is refreshed daily. You want to refresh it without blocking reads and ensure the data is current. Which command should you use?
You have a materialized view mv_orders that is refreshed daily. You want to refresh it without blocking reads and ensure the data is current. Which command should you use?
hard📝 Application Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Identify the requirement to avoid blocking reads
Using CONCURRENTLY allows refreshing without locking out reads on the materialized view.Step 2: Choose the correct syntax
REFRESH MATERIALIZED VIEW CONCURRENTLY mv_orders; uses the correct syntax to refresh concurrently. REFRESH MATERIALIZED VIEW mv_orders; blocks reads, REFRESH MATERIALIZED VIEW WITH NO DATA mv_orders; does not update the data to current state, and ALTER MATERIALIZED VIEW mv_orders REFRESH CONCURRENTLY; uses incorrect command structure.Final Answer:
REFRESH MATERIALIZED VIEW CONCURRENTLY mv_orders; -> Option BQuick Check:
Use CONCURRENTLY to refresh without blocking reads [OK]
Quick Trick: Use CONCURRENTLY to refresh without blocking reads [OK]
Common Mistakes:
- Using REFRESH without CONCURRENTLY causing locks
- Trying invalid syntax with ALTER
- Confusing WITH NO DATA option
Master "Views and Materialized Views" in PostgreSQL
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore PostgreSQL Quizzes