| From: | Chengpeng Yan <chengpeng_yan(at)outlook(dot)com> |
|---|---|
| To: | Marko Grujic <markoog(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #19507: Auto-named partition table constraint conflicts |
| Date: | 2026-06-05 13:08:57 |
| Message-ID: | 2856BB12-6389-4F06-9B35-576B838B669E@Outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Jun 5, 2026, at 21:01, Marko Grujic <markoog(at)gmail(dot)com> wrote:
>
> Hi Chengpeng,
>
> Thanks for the heads up.
>
> > My current plan is to preserve the
> existing behavior for explicitly named constraints, but make
> automatically generated names avoid conflicts that would be hit during
> recursive propagation. In other words, when considering a generated
> candidate name for the parent, the code should also consider whether
> using that name throughout the relevant partition/inheritance tree would
> run into a name conflict.
>
> Fyi, I also have a patch up already with that exact purpose: https://www.postgresql.org/message-id/CAOvwyF1JsmerqF6hA005rb6YLP%3DpQAPOJCAKnr398%3D0ReZG%3DAA%40mail.gmail.com
>
> Cheers,
> Marko
Sorry, I hadn't noticed that you had already posted a patch for this.
Thanks for pointing it out. I'll take a look and try to review it when I
get some time.
--
Best regards,
Chengpeng Yan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Grujic | 2026-06-05 13:11:25 | Re: BUG #19507: Auto-named partition table constraint conflicts |
| Previous Message | Marko Grujic | 2026-06-05 13:01:18 | Re: BUG #19507: Auto-named partition table constraint conflicts |