Re: [GENERAL] Cannot create matview when referencing another not-populated-yet matview in subquery - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: [GENERAL] Cannot create matview when referencing another not-populated-yet matview in subquery
Date
Msg-id 1383435902.37496.YahooMailNeo@web162905.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: [GENERAL] Cannot create matview when referencing another not-populated-yet matview in subquery  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-hackers
Kevin Grittner <kgrittn@ymail.com> wrote:
> Laurent Sartran <lsartran@gmail.com> wrote:

>> CREATE MATERIALIZED VIEW t1 AS SELECT text 'foo' AS col1
>>    WITH NO DATA;
>> CREATE MATERIALIZED VIEW t2b AS SELECT * FROM t1
>>    WHERE col1 = (SELECT LEAST(col1) FROM t1)
>>    WITH NO DATA;
>>
>> ERROR:  materialized view "t1" has not been populated
>> HINT:  Use the REFRESH MATERIALIZED VIEW command.
>
>> Is this behavior expected?
>
> No, and git bisect shows that it worked until commit
> 5194024d72f33fb209e10f9ab0ada7cc67df45b7.

Fix committed.  Thanks for the report!

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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Creating Empty Index
Next
From: Kevin Grittner
Date:
Subject: Re: missing locking in at least INSERT INTO view WITH CHECK