| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Cc: | hariprasath nallasamy <hariprasathnallasamy(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>, Nguyễn Trần Quốc Vinh <ntquocvinh(at)gmail(dot)com> |
| Subject: | Re: Incrementally refreshed materialized view |
| Date: | 2016-09-29 13:37:17 |
| Message-ID: | CAMjNa7faRe-vqTOqc9gNGHtwVFNXSAzeZCXRp+Waow0E4aNm0w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 29, 2016 at 8:10 AM, Nguyễn Trần Quốc Vinh <ntquocvinh(at)gmail(dot)com
> wrote:
> Dear,
>
> As it was recommended, we pushed our projects into github:
> https://github.com/ntqvinh/PgMvIncrementalUpdate.
>
> 1) Synchronous incremental update
> - For-each-row triggers are generated for all changing events on all
> underlying tables.
>
> 2) Asynchronous (deferred) incremental update
> - Triggers are generated for all changing events on all underlying tables
> to collect all changed rows
> - Other codes are generated for each matview-query to update the matview.
>
> We hope that our projects may be helpful for someone!
>
Very interesting. Does this support materialized views with recursive
queries? What about left joins? (not) exists? Aggregates? Window functions?
In reading up on the implementations in other databases, I was surprised by
some of the limitations imposed by DB2 / Oracle / Sql Server.
I'm trying to look through the code base to answer my questions, but it's
large enough that it may be easier to just ask first.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nguyễn Trần Quốc Vinh | 2016-09-29 13:56:41 | Re: Incrementally refreshed materialized view |
| Previous Message | Hanne Moa | 2016-09-29 13:10:52 | Getting the currently used sequence for a SERIAL column |