✳flâneur — a map of the web's best reading

PostgreSQL: Documentation: 16: REFRESH MATERIALIZED VIEW

postgresql.org · 499 words · saved by 1 readers

REFRESH MATERIALIZED VIEW completely replaces the contents of a materialized view. To execute this command you must be the owner of the materialized view. The old contents are discarded. If WITH DATA is specified (or defaults) the backing query is executed to provide the new data, and the materialized view is left in a scannable state. If WITH NO DATA is specified no new data is generated and the materialized view is left in an unscannable state. CONCURRENTLY and WITH NO DATA may not be specified together. Refresh the materialized view without locking out concurrent selects on the materialized view. Without this option a refresh which affects a lot of rows will tend to use fewer resources and complete more quickly, but could block other connections which are trying to read from the materialized view. This option may be faster in cases where a small number of rows are affected. This option is only allowed if there is at least one UNIQUE index on the materialized view which uses only col

PostgreSQL: Documentation: 18: REFRESH MATERIALIZED VIEW July 16, 2026: PostgreSQL 19 Beta 2 Released! Documentation → PostgreSQL 18 Supported Versions: Current ( 18 ) / 17 / 16 / 15 / 14 Development Versions: 19 / devel Unsupported versions: 13 / 12 / 11 / 10 / 9.6 / 9.5 / 9.4 / 9.3 REFRESH MATERIALIZED VIEW Prev Up SQL Commands Home Next REFRESH MATERIALIZED VIEW REFRESH MATERIALIZED VIEW — replace the contents of a materialized view Synopsis REFRESH MATERIALIZED VIEW [ CONCURRENTLY ] name [ WITH [ NO ] DATA ] Description REFRESH MATERIALIZED VIEW completely replaces the contents of a m

Explore this link on the map →

related reading