| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: 9.3 beta and materialized views |
| Date: | 2013-05-16 17:59:34 |
| Message-ID: | 1368727174.83283.YahooMailNeo@web162901.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
> Tom Lane wrote on 16.05.2013 19:36:
>>> As the materialized view should be a "table" that can be
>>> selected from, I wonder what the purpose of the rewrite rule
>>> is?
>>
>> To store the matview's definition for use in REFRESH.
>>
> Ah, right. Makes sense.
It will also be used to drive incremental update (in future
releases), as it does in every other product with materialized
views that I know of. In 9.3 we only got as far as explicit
REFRESH, but I hope to improve on that in 9.4.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Neyman | 2013-05-16 18:03:14 | Re: pg_upgrade link mode |
| Previous Message | AI Rumman | 2013-05-16 17:56:05 | Re: pg_upgrade link mode |