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

From Zhihong Yu
Subject Re: [PATCH] Partial foreign key updates in referential integrity triggers
Date
Msg-id CALNJ-vTF0+hhRYYB866jFWeHQeVSzjyADy0+VJzhQ6_-LnkypA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Partial foreign key updates in referential integrity triggers  (Paul Martinez <hellopfm@gmail.com>)
Responses Re: [PATCH] Partial foreign key updates in referential integrity triggers  (Paul Martinez <hellopfm@gmail.com>)
List pgsql-hackers


On Thu, Sep 2, 2021 at 12:11 PM Paul Martinez <hellopfm@gmail.com> wrote:
On Wed, Sep 1, 2021 at 4:11 AM Daniel Gustafsson <daniel@yesql.se> wrote:

> This patch no longer applies, can you please submit a rebased version?  It
> currently fails on catversion.h, to keep that from happening repeatedly you can
> IMO skip that from the patch submission.

Ah, understood. Will do that in the future. Attached are rebased patches, not
including catversion.h changes, for both the ON UPDATE/DELETE case, and the
ON DELETE only case.

- Paul
Hi,
+       case RI_TRIGTYPE_DELETE:
+           queryno = is_set_null
+               ? RI_PLAN_ONDELETE_SETNULL_DOUPDATE
+               : RI_PLAN_ONDELETE_SETDEFAULT_DOUPDATE;

Should the new symbols be renamed ?

RI_PLAN_ONDELETE_SETNULL_DOUPDATE -> RI_PLAN_ONDELETE_SETNULL_DODELETE 
RI_PLAN_ONDELETE_SETDEFAULT_DOUPDATE -> RI_PLAN_ONDELETE_SETDEFAULT_DODELETE

Cheers

pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: Skipping logical replication transactions on subscriber side
Next
From: Andrew Dunstan
Date:
Subject: Re: a misbehavior of partition row movement (?)