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

From Fujii Masao
Subject Re: odd behavior in materialized view
Date
Msg-id CAHGQGwHQuio9H3jhMGn01NujWor+PgLh9=3Z3K-qoqgKQGrU_Q@mail.gmail.com
Whole thread Raw
In response to Re: odd behavior in materialized view  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: odd behavior in materialized view  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-hackers
On Fri, Mar 8, 2013 at 1:52 AM, Kevin Grittner <kgrittn@ymail.com> wrote:
> 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.

Thanks!

I found one typo in the document of MV. Please see the attached patch.

Regards,

--
Fujii Masao

Attachment

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Materialized views WIP patch
Next
From: Andres Freund
Date:
Subject: REFRESH MATERIALIZED VIEW locklevel