Re: odd behavior in materialized view - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: odd behavior in materialized view
Date
Msg-id 1362675159.53476.YahooMailNeo@web162906.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: odd behavior in materialized view  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: odd behavior in materialized view  (Fujii Masao <masao.fujii@gmail.com>)
Re: odd behavior in materialized view  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> wrote:

> Thanks! I confirmed that the problem that I reported has
> disappeared in HEAD.
>
> Unfortunately I found another odd behavior. When I accessed the
> MV after VACUUM ANALYZE, I got the following error.
>
>     ERROR:  materialized view "hogeview" has not been populated
>     HINT:  Use the REFRESH MATERIALIZED VIEW command.
>     STATEMENT:  select * from hogeview where i < 10;
>
> The test case to reproduce that is:
>
> create table hoge (i int);
> insert into hoge values (generate_series(1,100000));
> create materialized view hogeview as select * from hoge where i % 2 = 0;
> create index hogeviewidx on hogeview (i);
> delete from hoge;
> refresh materialized view hogeview;
> select * from hogeview where i < 10;
> vacuum analyze;
> select * from hogeview where i < 10;
>
> The last SELECT command caused the above error.

Thanks.  Will fix.

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Support for REINDEX CONCURRENTLY
Next
From: "David E. Wheeler"
Date:
Subject: Re: Materialized views WIP patch