public inbox for [email protected]  

help / color / mirror / Atom feed

From: Marko Grujic <[email protected]>
To: Chengpeng Yan <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: BUG #19507: Auto-named partition table constraint conflicts
Date: Fri, 5 Jun 2026 15:11:25 +0200
Message-ID: <CAKQrOnp2H4FpzagV1CFyoWbja1jLcwCmuufipw6OiVsWgF+_Cg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<CAKQrOnr621sTrm4=uqRikq=ZB+-qEb4tq5opPQTiF8J+xr-cwg@mail.gmail.com>
	<[email protected]>

No worries; yeah, a review would be greatly appreciated, thank you.

On Fri, Jun 5, 2026 at 3:09 PM Chengpeng Yan <[email protected]>
wrote:

>
> > On Jun 5, 2026, at 21:01, Marko Grujic <[email protected]> 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%40ma...
> >
> > 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

view thread (5+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: BUG #19507: Auto-named partition table constraint conflicts
  In-Reply-To: <CAKQrOnp2H4FpzagV1CFyoWbja1jLcwCmuufipw6OiVsWgF+_Cg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox