From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | David Christensen <david(at)endpoint(dot)com> |
Cc: | Pavel Baroš <baros(dot)p(at)seznam(dot)cz>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: GSoC - code of implementation of materialized views |
Date: | 2010-06-30 01:18:53 |
Message-ID: | AANLkTinC3fvLDVn3nQfLLRcB2BaTdK6H0X50aTtsGJAh@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/6/29 David Christensen <david(at)endpoint(dot)com>:
> Do we see supporting the creation of a materialized view from a regular view, as in ALTER VIEW regular_view SET MATERIALIZED or some such?
I'm not sure. I think we should focus our efforts on (1) getting it
to work at all and then (2) improving the performance of the refresh
operation, which will doubtless be pessimal in the initial
implementation. Those are big enough problems that I'm not inclined
to spend much thought on bells and whistles at this point.
> Since we're treating this as a distinct object type, instead of repeatedly typing "MATERIALIZED VIEW", is there a possibility of introducing a keyword alias "MATVIEW" without complicating the grammar/code all that much, or is that frowned upon? Paintbrushes, anyone?
-1 from me, but IJWH.
By the way, does the SQL standard say anything about materialized views?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-06-30 01:42:06 | Re: Cannot cancel the change of a tablespace |
Previous Message | Bruce Momjian | 2010-06-30 00:33:39 | Re: Propose Beta3 for July |