Re: Feature: triggers on materialized views - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Feature: triggers on materialized views
Date
Msg-id 20190401070610.GC16093@paquier.xyz
Whole thread Raw
In response to Re: Feature: triggers on materialized views  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, Mar 21, 2019 at 03:41:08PM -0400, Robert Haas wrote:
> Yeah.  The fact that a concurrent refresh currently does DELETE+INSERT
> rather than UPDATE is currently an implementation detail.  If you
> allow users to hook up triggers to the inserts, then suddenly it's no
> longer an implementation detail: it is a user-visible behavior that
> can't be changed in the future without breaking backward
> compatibility.

We are visibly going nowhere for this thread for v12, so I have marked
the proposal as returned with feedback.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Progress reporting for pg_verify_checksums
Next
From: "Jamison, Kirk"
Date:
Subject: RE: Timeout parameters