# Materialized view

> A stored result of a query, kept on disk and refreshed on a schedule, so a report reads the answer instead of scanning the tables. It is fast, and it is only as fresh as the last refresh.

Data

## In Quorum

Materialized views research adds a view to a Database’s card. A report scans the stored view for half the CPU (10), but 5% of report answers are stale, from before the last refresh. It is the Database-side twin of the Data Warehouse, with the same cheap scans and no second system.

## Design

[Data Warehouse and views](https://wiki.playquorum.dev/design/07-data-tier.md#data-warehouse)

## Read next

[OLTP and OLAP](https://wiki.playquorum.dev/glossary/oltp-and-olap.md), [CDC (change data capture)](https://wiki.playquorum.dev/glossary/cdc-change-data-capture.md), [Cache hit rate](https://wiki.playquorum.dev/glossary/cache-hit-rate.md), [Read replica](https://wiki.playquorum.dev/glossary/read-replica.md)

## Learn more

- [PostgreSQL docs: Materialized views](https://www.postgresql.org/docs/current/rules-materializedviews.html)

## See also

- [Glossary](https://wiki.playquorum.dev/glossary.md)

Source: https://wiki.playquorum.dev/glossary/materialized-view