Re: [PATCH] Partial foreign key updates in referential integrity triggers

From: David Steele <david(at)pgmasters(dot)net>
To: Paul Martinez <paulmtz(at)google(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Partial foreign key updates in referential integrity triggers
Date: 2021-03-18 13:52:16
Message-ID: 9e8cf67b-f7a4-cfbf-e1f9-bc0542813014@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)pgmasters(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2021-03-18 13:54:11 Re: fdatasync performance problem with large number of DB files
Previous Message Bruce Momjian 2021-03-18 13:47:29 Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?