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-23 14:05:03 |
Message-ID: | 209cca61-ef27-16ef-3e8d-07fefbc31faa@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/18/21 9:52 AM, David Steele wrote:
> 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.
This entry has been moved to the 2021-07 CF with status Needs Review.
Regards,
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Andrei Zubkov | 2021-03-23 14:08:32 | Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements |
Previous Message | Alvaro Herrera | 2021-03-23 13:36:58 | Re: WIP: BRIN multi-range indexes |