Re: Implementing Incremental View Maintenance - Mailing list pgsql-hackers

From Yugo NAGATA
Subject Re: Implementing Incremental View Maintenance
Date
Msg-id 20220422112939.dc2a3a4e559defc9b43024d0@sraoss.co.jp
Whole thread Raw
In response to Re: Implementing Incremental View Maintenance  (Greg Stark <stark@mit.edu>)
Responses Re: Implementing Incremental View Maintenance
List pgsql-hackers
Hi,

On Fri, 1 Apr 2022 11:09:16 -0400
Greg Stark <stark@mit.edu> wrote:

> This patch has bitrotted due to some other patch affecting trigger.c.
> 
> Could you post a rebase?
> 
> This is the last week of the CF before feature freeze so time is of the essence.

I attached a rebased patch-set.

Also, I made the folowing changes from the previous.

1. Fix to not use a new deptye

In the previous patch, we introduced a new deptye 'm' into pg_depend.
This deptype was used for looking for IVM triggers to be removed at
REFRESH WITH NO DATA. However, we decided to not use it for reducing
unnecessary change in the core code. Currently, the trigger name and
dependent objclass are used at that time instead of it.

As a result, the number of patches are reduced to nine from ten.

2. Bump the version numbers in psql and pg_dump

This feature's target is PG 16 now.

Regards,
Yugo Nagata


-- 
Yugo NAGATA <nagata@sraoss.co.jp>

Attachment

pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: Replace open mode with PG_BINARY_R/W/A macros
Next
From: Tom Lane
Date:
Subject: Re: Replace open mode with PG_BINARY_R/W/A macros