Avoid unnecessary name conflicts with NOT NULL constraints that make pg_upgrade fail

Edit
ID 6495
Title Avoid unnecessary name conflicts with NOT NULL constraints that make pg_upgrade fail
CI (CFBot) Summary
Stats (from CFBot) Patch version: v2, Patch count: 1, First patch: +29−6, All patches: +29−6
Tags Bugfix
Created 2026-02-17 09:53:02
Last modified 2026-02-17 09:53:03 (10 hours ago)
Latest email 2026-02-10 00:37:09 (1 week ago)
Status
PG19-Final (2026-03-01 – 2026-03-31): Needs review
Target version stable
Authors Laurenz Albe (laurenz)
Reviewers Become reviewer
Committer
Links
Emails
BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
First at 2026-02-04 17:33:21 by PG Bug reporting form <noreply at postgresql.org>
Latest at 2026-02-10 00:37:09 by Michael Paquier <michael at paquier.xyz>
Latest attachment (v2-0001-Avoid-name-collision-with-NOT-NULL-constraints.patch) at 2026-02-05 16:52:50 from Laurenz Albe <laurenz.albe at cybertec.at>
    Attachment (v2-0001-Avoid-name-collision-with-NOT-NULL-constraints.patch) at 2026-02-05 16:52:50 from Laurenz Albe <laurenz.albe at cybertec.at> (Patch: Yes)
    Attachment (v1-0001-Avoid-name-collision-with-NOT-NULL-constraints.patch) at 2026-02-05 14:58:50 from Laurenz Albe <laurenz.albe at cybertec.at> (Patch: Yes)
History
When Who What
2026-02-17 09:53:03 Laurenz Albe (laurenz) Attached mail thread 19393-6a82427485a744cf@postgresql.org
2026-02-17 09:53:02 Laurenz Albe (laurenz) Created patch record
Edit