RE: why can't a table be part of the same publication as its schema - Mailing list pgsql-hackers

From houzj.fnst@fujitsu.com
Subject RE: why can't a table be part of the same publication as its schema
Date
Msg-id OS0PR01MB57162E862758402F978725CD944B9@OS0PR01MB5716.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: why can't a table be part of the same publication as its schema  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: why can't a table be part of the same publication as its schema
List pgsql-hackers
On Saturday, September 17, 2022 11:22 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> 
> On Fri, Sep 16, 2022 at 1:09 PM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
> wrote:
> >
> > Attach the new version patch which addressed above comments and ran
> pgident.
> > I also improved some codes and documents based on some comments given
> > by Vignesh and Peter offlist.
> >
> 
> Thanks, the patch looks mostly good to me. I have made a few cosmetic changes
> and edited a few comments. I would like to push this to HEAD and backpatch it
> to 15 by Tuesday unless there are any comments. I think we should back patch
> this because otherwise, users will see a change in behavior in 16 but if others
> don't think the same way then we can consider pushing this to HEAD only.

Thanks for the patch.
I rebased it based on PG15 and here is the patch.

Best regards,
Hou zj

Attachment

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: Make mesage at end-of-recovery less scary.
Next
From: Peter Eisentraut
Date:
Subject: Re: ICU for global collation