Are redshift auto materialized views schema bound?

Question

I can’t create a user defined materialized view with no schema binding, and since my etl process involves automatically recreating tables when the source ddl has changed, that means I can’t use user defined materialized views. How do auto materialized views that just became generally available last month get around this restriction?

MilindOke · Answer

In this scenario Redshift will not be able to really create auto MV's for the part where tables are being dropped and recreated. But further down the line, after ETL has completed, if you have subsequent user queries which are more or less of repeatable nature then Redshift will be able to leverage this feature and create some auto MV's that will boost user query performance.

Adeel · Answer

Yes, since materialized views (MVs) are physical tables, unlike regular views, they depend on the original tables. If you try to drop any column from the original table, the MV will prevent you from doing so due to these dependencies.

Enter image description here

![Enter image description here](/media/postImages/original/IMoinracmWQEqee-B9m8ROKA)

Are redshift auto materialized views schema bound?

Relevant content