Re: Implementing Incremental View Maintenance

From: Adam Brusselback <adambrusselback(at)gmail(dot)com>
To: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Subject: Re: Implementing Incremental View Maintenance
Date: 2020-10-22 14:07:29
Message-ID: CAMjNa7cX8-++asotpqX1BE24J-KUqe7Dv38CHa47TPdfmSqV5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hey there Yugo,
I've asked a coworker to prepare a self contained example that encapsulates
our multiple use cases.

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
reflected.

As soon as my coworker gets that example built up I'll send a followup with
it attached.
Thank you,
Adam Brusselback

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2020-10-22 14:20:49 Re: Is Recovery actually paused?
Previous Message Robert Haas 2020-10-22 14:06:48 Re: new heapcheck contrib module