Postgresql has storage parameters for tables and materialized views. This is used specifically by timescaledb to create continuous aggregate materialized views for timeseries data. Adding a storage parameters argument to PGMaterializedView doesn't seem complicated and opens a whole new usage scenario with timescaledb. I'd be happy to make the PR.