> On Jun 5, 2026, at 21:01, Marko Grujic <markoog@gmail.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.