|From:||Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>|
|To:||Adam Brusselback <adambrusselback(at)gmail(dot)com>|
|Cc:||Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>|
|Subject:||Re: Implementing Incremental View Maintenance|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Thu, 22 Oct 2020 10:07:29 -0400
Adam Brusselback <adambrusselback(at)gmail(dot)com> wrote:
> Hey there Yugo,
> I've asked a coworker to prepare a self contained example that encapsulates
> our multiple use cases.
Thank you very much!
> The immediate/eager approach is exactly what we need, as within the same
> transaction we have statements that can cause one of those "materialized
> tables" to be updated, and then sometimes have the need to query that
> "materialized table" in a subsequent statement and need to see the changes
The proposed patch provides the exact this feature and I think this will meet
> As soon as my coworker gets that example built up I'll send a followup with
> it attached.
Great! We are looking forward to it.
Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
|Next Message||Michael Paquier||2020-10-23 08:02:11||Re: "unix_socket_directories" should be GUC_LIST_INPUT?|
|Previous Message||Peter Eisentraut||2020-10-23 07:49:15||Re: Hash support for row types|