Manual Reference Pages - REFRESH_MATERIALIZED_VIEW (7)

CONTENTS

REFRESH MATERIALIZED VIEW
completely replaces the contents of a 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.

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 column names and includes all rows; that is, it must not index on any expressions nor include a
WHERE
clause.

This option may not be used when the materialized view is not already populated.

Even with this option only one
REFRESH
at a time may run against any one materialized view.

name

The name (optionally schema-qualified) of the materialized view to refresh.

While the default index for future
CLUSTER(7)
operations is retained,
REFRESH MATERIALIZED VIEW
does not order the generated rows based on this property. If you want the data to be ordered upon generation, you must use an
ORDER BY
clause in the backing query.