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

From Peter Eisentraut
Subject Re: [PATCH] Partial foreign key updates in referential integrity triggers
Date
Msg-id 9e077514-7f9a-ebba-38d8-2bda3b697377@enterprisedb.com
Whole thread Raw
In response to Re: [PATCH] Partial foreign key updates in referential integrity triggers  (Paul Martinez <hellopfm@gmail.com>)
List 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.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: pg_get_publication_tables() output duplicate relid
Next
From: Amit Kapila
Date:
Subject: Re: Fix a bug in DecodeAbort() and improve input data check on subscriber.