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
da...@pgmasters.net
[1]
https://www.postgresql.org/message-id/20190216054526.zss2cufdxfeudr4i%40alap3.anarazel.de
