I wrote:
> Let's say there is a table and matview like this:
>
> create table foo (fooid int primary key, val int not null);
> create materialized view bar as select distinct val from foo;
Some of the subsequent text doesn't make sense unless that
materialized view has an index, like this:
create unique index bar_val on bar (val);
Without such an index, it would need to use a plan which scanned
the entire bar relation for any maintenance. Apologies for the
omission and any confusion it caused.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
