| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> | 
|---|---|
| To: | "Pradhan, Sabin" <Sabin(dot)Pradhan(at)finra(dot)org> | 
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> | 
| Subject: | Re: fast refresh materialized view | 
| Date: | 2015-11-15 11:36:40 | 
| Message-ID: | CAB7nPqTc=-MQVoFAuPq66C=+op0KePVgCGGEJ5x53y6hu8yg2Q@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Sat, Nov 14, 2015 at 7:01 AM, Pradhan, Sabin <Sabin(dot)Pradhan(at)finra(dot)org> wrote:
> Does postgres  has fast refresh materialized view  that supports incremental
> refresh. In oracle  , this is achieve  by materialized view log. Not sure
> how to  implement it in postgres.
No. Postgres offers just the possibility to refresh materialized views
while taking a lock on it that allows reads to continue running on it
WITH REFRESH MATERIALIZED VIEW CONCURRENTLY. A necessary condition is
that a UNIQUE index needs to be created on it.
> Confidentiality Notice:: This email, including attachments, may include
> non-public, proprietary, confidential or legally privileged information. If
> you are not an intended recipient or an authorized agent of an intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of the information contained in or transmitted with this e-mail is
> unauthorized and strictly prohibited. If you have received this email in
> error, please notify the sender by replying to this message and permanently
> delete this e-mail, its attachments, and any copies of it immediately. You
> should not retain, copy or use this e-mail or any attachment for any
> purpose, nor disclose all or any part of the contents to any other person.
This is a public mailing list.
-- 
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Luya | 2015-11-15 13:44:10 | Re: | 
| Previous Message | Tom Lane | 2015-11-14 17:19:11 | Re: Poor performance on 9.4.4 when matching multiple columns from left side of LATERAL join |