Re: [PATCH] Partial foreign key updates in referential integrity triggers - Mailing list pgsql-hackers

From David Steele
Subject Re: [PATCH] Partial foreign key updates in referential integrity triggers
Date
Msg-id 9e8cf67b-f7a4-cfbf-e1f9-bc0542813014@pgmasters.net
Whole thread Raw
In response to [PATCH] Partial foreign key updates in referential integrity triggers  (Paul Martinez <paulmtz@google.com>)
Responses Re: [PATCH] Partial foreign key updates in referential integrity triggers  (David Steele <david@pgmasters.net>)
List pgsql-hackers
On 1/5/21 4:40 PM, Paul Martinez wrote:
> 
> I've created a patch to better support referential integrity constraints when
> using composite primary and foreign keys. This patch allows creating a foreign
> key using the syntax:

<snip>

> I previously proposed this feature about a year ago [1], but I don't feel like
> the arguments against it were very strong.

Perhaps not, but Tom certainly didn't seem in favor of this feature, at 
the least.

Since the patch has not attracted any review/comment I propose to move 
it to the next CF since it doesn't seem a likely candidate for PG14.

I'll do that on March 23 unless there are arguments to the contrary.

Regards,
-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Next
From: Bruce Momjian
Date:
Subject: Re: fdatasync performance problem with large number of DB files