> I've thought for some time that, given that it can't reproduce the MV
> states exactly, pg_dump shouldn't even try. I think it would be more
> useful to have two operating modes selectable by command line switch:
> refresh all matviews, or refresh none of them.
This seems like a reasonable sol
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> I've thought for some time that, given that it can't reproduce the MV
> states exactly, pg_dump shouldn't even try. I think it would be more
> useful to have two operating modes selectable by command line switch:
> refresh all matviews, or refresh none of t
Tom Lane wrote:
> Consider the following scenario:
>
> create table t1 as select 1 as x;
> create materialized view mv1 as select * from t1;
> create materialized view mv2 as select * from mv1;
> create materialized view mv3 as select * from mv2;
> refresh materialized view mv1 with no data;
>
