RisingWave Community - Is it wise to use multiple materialized views in Postgres and how long would you expect a create MV with 170 million rows to execute?

Using multiple materialized views in Postgres can be a good strategy to improve query performance by pre-computing and storing results.
When creating an MV with 170 million rows, the execution time can vary based on factors like hardware resources, complexity of the query, and indexing. It's recommended to optimize the query and consider the hardware setup to reduce the creation time.
Creating smaller MVs from larger ones can help in filtering the total rows and improving performance, as seen in Doug's case with ~60 million rows and 81 columns.
It's important to balance the number of MVs created to avoid excessive overhead and maintenance complexity.
Deployment setup, including the number of cores and available resources, can impact the execution time of creating materialized views with large datasets.