Horton

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

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Paul Martinez <hellopfm@gmail.com>, Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: Zhihong Yu <zyu@yugabyte.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-12-08T10:29:11Z
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.

Commits

  1. Allow specifying column list for foreign key ON DELETE SET actions

  2. doc: Add referential actions to CREATE/ALTER TABLE synopsis