I'm wondering why the support for MatViews with IVM is not supported in cases where the underlying query is also based on MatViews.
From the README:
The base tables must be simple tables. Views, materialized views, inheritance parent tables, partitioned tables, partitions, and foreign tables can not be used.
Is there a reason or challenge we can maybe address to improve this support? Or is it "just" a limitation in regards to unknown behaviour of the extension? (but I think it has more to do with rewrite rules, but I'm not that familiar with the internals here tbh)
We're currently building a project upon an existing database with multiple terabytes of data including historical data; forcing us to have intermediate MatViews in order to achieve short refresh cycles.
I'm wondering why the support for MatViews with IVM is not supported in cases where the underlying query is also based on MatViews.
From the README:
Is there a reason or challenge we can maybe address to improve this support? Or is it "just" a limitation in regards to unknown behaviour of the extension? (but I think it has more to do with rewrite rules, but I'm not that familiar with the internals here tbh)
We're currently building a project upon an existing database with multiple terabytes of data including historical data; forcing us to have intermediate MatViews in order to achieve short refresh cycles.