| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | "hari(dot)prasath" <hari(dot)prasath(at)zohocorp(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Incremental refresh of materialized view - Patch |
| Date: | 2016-05-12 14:25:57 |
| Message-ID: | CACjxUsP8J6bA4RKxbmwujTVMwMZrgR3AZ7yP5F2XkB-f9w7K7Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 12, 2016 at 1:05 AM, hari.prasath <hari(dot)prasath(at)zohocorp(dot)com> wrote:
> However if the same methods in matview.c
> OpenMatViewIncrementalMaintenance & CloseMatViewIncrementalMaintenance are
> mad extern its possible to do DML from the patches like i am building now.
>
> Is there any other way of doing DML operations on materialized views
> from patch.?
If you want to maintain materialized data using application-level
DML, you should use a table, not a materialized view. Once there
is built-in incremental maintenance, allowing DML will just make
the contents of a materialized view completely unreliable.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-05-12 14:49:06 | Re: Perf Benchmarking and regression. |
| Previous Message | Fabrízio de Royes Mello | 2016-05-12 12:48:58 | Re: Error during restore - dump taken with pg_dumpall -c option |