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

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Paul Martinez <hellopfm(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Cc: Zhihong Yu <zyu(at)yugabyte(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Partial foreign key updates in referential integrity triggers
Date: 2021-12-08 10:29:11
Message-ID: 9e077514-7f9a-ebba-38d8-2bda3b697377@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02.12.21 01:17, Paul Martinez wrote:
> Regarding that specific example, in a production scenario, yes, the
> DELETE command should reference both columns. And if used for
> documentation both columns should be referenced for clarity/correctness.

Ok, thanks. I have updated your example accordingly and included it in
the patch, which I have now committed.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-12-08 11:00:06 Re: Fix a bug in DecodeAbort() and improve input data check on subscriber.
Previous Message Amit Kapila 2021-12-08 10:16:50 Re: pg_get_publication_tables() output duplicate relid