| From: | Haibo Yan <tristan(dot)yim(at)gmail(dot)com> |
|---|---|
| To: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
| Cc: | Andrew Krylosov <krylosov(dot)andrew(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: addFkRecurseReferencing use unassigned fkconstraint->fk_with_period value |
| Date: | 2026-10-10 14:38:34 |
| Message-ID: | CABXr29EHmV3WvUR2uOZKi1RgeQp3w43GKfFrJSwnsWYOReMQSg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 8, 2026 at 10:22 PM Paul A Jungwirth
<pj(at)illuminatedcomputing(dot)com> wrote:
>
> On Mon, Sep 28, 2026 at 11:18 PM Haibo Yan <tristan(dot)yim(at)gmail(dot)com> wrote:
> >
> changed the wording to "with pre-existing
> > rows" and moved the NOT VALID / NOT ENFORCED tests after the
> > pg_get_constraintdef checks.
> >
> > There are no code changes from v1.
>
> This looks good to me too. Andres reported the VALIDATE CONSTRAINT
> case in [0], but it's nice to have fixes to all three cases in one
> place.
>
> If you want, here is a v3 with a less verbose commit message. Also I
> added the note suggested by Andrew, which seems worth including in
> release notes.
>
> [0] https://www.postgresql.org/message-id/sesqxzfcujkcnrwpir5xvhy7iamhsbjiqt6r2xqmb7hqkulte6%40bbuc42qzanzs
>
> Yours,
>
> --
> Paul ~{:-)
> pj(at)illuminatedcomputing(dot)com
Hi Paul,
Thanks for picking this up and preparing v3.
The changes look good to me. One minor wording nit in the commit
message: "despite covering violating rows" might be clearer as
"despite containing violating rows".
Otherwise, v3 looks good to me.
Thanks,
Haibo
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haibo Yan | 2026-10-10 15:27:05 | Re: [PG19] Wrong results from NOT NULL-based expression simplification |
| Previous Message | Andrew Dunstan | 2026-10-10 11:29:47 | Re: Allow table AMs to define their own reloptions |