Re: Foreign key validation failure in 18beta1 - Mailing list pgsql-hackers

From jian he
Subject Re: Foreign key validation failure in 18beta1
Date
Msg-id CACJufxE0KRLtrapdQOYw1TW+BbfcbLrng7S7fzDz+M_T1RDknw@mail.gmail.com
Whole thread Raw
In response to Re: Foreign key validation failure in 18beta1  (Amul Sul <sulamul@gmail.com>)
Responses Re: Foreign key validation failure in 18beta1
List pgsql-hackers
On Tue, Jun 3, 2025 at 12:14 PM Amul Sul <sulamul@gmail.com> wrote:
> >
>
> I found a third approach that requires only a few changes. The key
> idea is to determine the root referenced table and pass it to
> QueueFKConstraintValidation(). We would then enqueue phase 3
> validation only if the constraint tuple’s confrelid matches that root
> table -- similar to what is doing in ATExecAlterConstrEnforceability().
>
> This would also ensure that the logic for adding/skipping phase 3
> validation is consistent in both places.
>
indeed!

v7 is way more intuitive compared with v5, v6.
The commit message also looks fine.



pgsql-hackers by date:

Previous
From: Xuneng Zhou
Date:
Subject: Re: Proposal: Limitations of palloc inside checkpointer
Next
From: Shubham Khanna
Date:
Subject: Enhance pg_createsubscriber to create required standby.