Re: odd behavior in materialized view

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: odd behavior in materialized view
Date: 2013-03-07 16:52:39
Message-ID: 1362675159.53476.YahooMailNeo@web162906.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2013-03-07 17:14:57 Re: Materialized views WIP patch
Previous Message Andres Freund 2013-03-07 16:46:02 Re: Support for REINDEX CONCURRENTLY