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.”

Preferences
Contact Us
Feedback
AWS Documentation
Create an AWS Account
Limitations for using the SUPER data type with materialized views - Amazon Redshift
This page has not been translated into your language. Request translation

Limitations for using the SUPER data type with materialized views

PDFRSS

With Amazon Redshift, you can create materialized views with the SUPER data type to pre-compute complex queries and improve query performance. The SUPER data type lets you store the result set of a query as a flat data structure, enabling faster access and processing.

The following sections provide details on limitations and best practices for using the SUPER data type with materialized views in Amazon Redshift.

Materialized views in Amazon Redshift don't have any specific limitations with respect to PartiQL or SUPER.

For information about general SQL limitations when creating materialized views, see Limitations.

For information about general SQL limitations on incremental refresh of materialized views, see Limitations for incremental refresh.

Next topic:

Machine learning

Need help?

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