| From: | Marko Grujic <marko(dot)grujic(at)enterprisedb(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Marko Grujic <markoog(at)gmail(dot)com> |
| Subject: | Re: [PATCH v1] [BUG #19507] Prevent constraint name conflicts in partition trees spanning multiple schemas |
| Date: | 2026-06-04 11:11:22 |
| Message-ID: | CAOvwyF1JsmerqF6hA005rb6YLP=pQAPOJCAKnr398=0ReZG=AA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Updating the patch with some minor refinements:
- remove redundant list_free(inheritors)
- use foreach_oid in place of foreach
- explain input args to the new ChooseConstraintNameForRelation function
Also reporting that I'm seeing this bug manifest all the way back to PG14
(haven't looked further since versions older than that are EOLd).
Importantly, besides latest master, the current patch applies cleanly to
PG18 (plain git apply).
In addition, it also applies without any conflicts to PG17, PG16 and PG15
(git apply --3way).
It doesn't apply cleanly to PG14 (missing src/test/regress/{sql,
expected}/constraints.{sql, out} files),
but since its EOL is a couple of months away I don't think back-porting
this to it is that important anyway.
Thanks,
Marko
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Prevent-constraint-name-conflicts-in-partition-trees.patch | application/octet-stream | 16.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nazir Bilal Yavuz | 2026-06-04 11:12:32 | Re: Heads Up: cirrus-ci is shutting down June 1st |
| Previous Message | Nisha Moond | 2026-06-04 10:54:43 | Re: Proposal: Conflict log history table for Logical Replication |