From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Mitar <mmitar(at)gmail(dot)com>, Nguyễn Trần Quốc Vinh <ntquocvinh(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Re: Feature: triggers on materialized views |
Date: | 2019-03-07 08:13:01 |
Message-ID: | 0ba15896-e29a-2a13-bab1-4a421cfb2e1a@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/5/19 11:57 PM, Mitar wrote:
>
> Having better updating of materialized views using incremental
> approach would really benefit my use case as well. Then triggers being
> added through my patch here on materialized view itself could
> communicate those changes which were done to the client. If I
> understand things correctly, this IVM would benefit the speed of how
> quickly we can do refreshes, and also if would allow that we call
> refresh on a materialized view for every change on the source tables,
> knowing exactly what we have to update in the materialized view.
> Really cool. I also see that there was recently more discussion about
> IVM on the mailing list. [1]
There doesn't seem to be consensus on whether or not we want this patch.
Peter has issues with the way it works and Andres [1] thinks it should
be pushed to PG13 or possibly rejected.
I'll push this to PG13 for now.
Regards,
--
-David
david(at)pgmasters(dot)net
[1]
https://www.postgresql.org/message-id/20190216054526.zss2cufdxfeudr4i%40alap3.anarazel.de
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2019-03-07 08:14:23 | Re: Making all nbtree entries unique by having heap TIDs participate in comparisons |
Previous Message | Fabien COELHO | 2019-03-07 08:10:47 | Re: Re: [HACKERS] proposal: schema variables |