AWS redshift documentation change
Summary
Added cascading refresh functionality with RESTRICT/CASCADE options and security controls
Security assessment
Introduces security controls by specifying that only owners/superusers can use CASCADE option, documenting access control requirements for the new feature.
Diff
diff --git a/redshift/latest/dg/materialized-view-refresh-sql-command.md b/redshift/latest/dg/materialized-view-refresh-sql-command.md index 47880a8eb..d37c8b2fe 100644 --- a//redshift/latest/dg/materialized-view-refresh-sql-command.md +++ b//redshift/latest/dg/materialized-view-refresh-sql-command.md @@ -5 +5,3 @@ -SyntaxParametersUsage notesIncremental refresh for materialized views in a datashareLimitations for incremental refreshExamples +SyntaxParametersUsage notesCascading refreshIncremental refresh for materialized views in a datashareLimitations for incremental refreshExamples + +Amazon Redshift will no longer support the creation of new Python UDFs starting November 1, 2025. If you would like to use Python UDFs, create the UDFs prior to that date. Existing Python UDFs will continue to function as normal. For more information, see the [ blog post ](https://aws.amazon.com/blogs/big-data/amazon-redshift-python-user-defined-functions-will-reach-end-of-support-after-june-30-2026/). @@ -20 +22 @@ For more information about materialized views, see [Materialized views in Amazon - REFRESH MATERIALIZED VIEW _mv_name_ + REFRESH MATERIALIZED VIEW _mv_name_ [ RESTRICT | CASCADE ] @@ -28,0 +31,10 @@ The name of the materialized view to be refreshed. +RESTRICT + + +Optional keyword. Refreshes the specified materialized view but not its dependent materialized views. The default if neither RESTRICT nor CASCADE is specified. + +CASCADE + + +Optional keyword. Refreshes the specified materialized view and all its dependent materialized views. + @@ -54,0 +67,17 @@ Some operations in Amazon Redshift interact with materialized views. Some of the +## Cascading refresh + +The CASCADE option refreshes the specified materialized view and all its dependent materialized views, in order of dependence: base MVs are REFRESHed before the MVs on top (topological ordering). This allows you to update a nested set of materialized views in a single command. + +The RESTRICT option (the default if neither RESTRICT nor CASCADE is specified) refreshes only the specified materialized view. + +When using the CASCADE option, the following rules apply: + + * Only the owner of the materialized view or a superuser can execute the `REFRESH MATERIALIZED VIEW ... CASCADE`command. + + * If any of the materialized views in the cascade cannot be refreshed, the entire cascade operation will stop. + + + + +The cascading refresh functionality is only supported for MVs nested on top of local and streaming materialized views. Materialized views with other source types, such as Spectrum or Data Sharing, are not supported in cascade mode. CASCADE executes refresh in a single transaction for all nested MVs. + @@ -108,0 +138,4 @@ The following example refreshes the `tickets_mv` materialized view. +The following example refreshes the `products_mv` materialized view and all its dependent materialized views: + + + REFRESH MATERIALIZED VIEW products_mv CASCADE;