Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

SVV_MV_INFO

Focus mode
SVV_MV_INFO - Amazon Redshift

The SVV_MV_INFO table contains a row for every materialized view, whether the data is stale, and state information.

For more information about materialized views, see Materialized views in Amazon Redshift.

SVV_MV_INFO is visible to all users. Superusers can see all rows; regular users can see only their own data. For more information, see Visibility of data in system tables and views.

Table columns

Column name Data type Description
database_name char(128) The database that contains the materialized view.
schema_name char(128) The schema of the database.
user_name char(128) The user who owns the materialized view.
name char(128) The materialized view name.
is_stale char(1) A t indicates that the materialized view is stale. A stale materialized view is one where the base tables have been updated but the materialized view hasn't been refreshed. This information might not be accurate if a refresh hasn't been run since the last restart.
state integer The state of the materialized view as follows:
  • 0 – The materialized view is fully recomputed when refreshed.

  • 1 – The materialized view is incremental.

  • 101 – The materialized view can't be refreshed due to a dropped column. This constraint applies even if the column isn't used in the materialized view.

  • 102 – The materialized view can't be refreshed due to a changed column type. This constraint applies even if the column isn't used in the materialized view.

  • 103 – The materialized view can't be refreshed due to a renamed table.

  • 104 – The materialized view can't be refreshed due to a renamed column. This constraint applies even if the column isn't used in the materialized view.

  • 105 – The materialized view can't be refreshed due to a renamed schema.

autorewrite char(1) A t indicates that the materialized view is eligible for automatic rewriting of queries.
autorefresh char(1) A t indicates that the materialized view can be automatically refreshed.

Sample query

To view the state of all materialized views, run the following query.

select * from svv_mv_info;

This query returns the following sample output.

database_name | schema_name | user_name | name | is_stale | state | autorefresh | autorewrite --------------+-------------------------+-----------+---------+-----------+-------+-------------+---------------- dev | test_ivm_setup | catch-22 | mv | f | 1 | 1 | 0 dev | test_ivm_setup | lotr | old_mv | t | 1 | 0 | 1

On this page

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.