RE: [PATCH]Comment improvement in publication.sql - Mailing list pgsql-hackers

From tanghy.fnst@fujitsu.com
Subject RE: [PATCH]Comment improvement in publication.sql
Date
Msg-id TYCPR01MB61284B10A090E273B4C89644FB469@TYCPR01MB6128.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: [PATCH]Comment improvement in publication.sql  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
On Monday, December 13, 2021 11:53 PM vignesh C <vignesh21@gmail.com> wrote:
> 
> On Wed, Dec 8, 2021 at 11:07 AM tanghy.fnst@fujitsu.com
> <tanghy.fnst@fujitsu.com> wrote:
> >
> > On Wednesday, December 8, 2021 1:49 PM, vignesh C <vignesh21@gmail.com>
> wrote:
> >
> > > The patch no longer applies, could you post a rebased patch.
> >
> > Thanks for your kindly reminder. Attached a rebased patch.
> > Some changes in v4 patch has been fixed by 5a28324, so I deleted those
> changes.
> 
> Thanks for the updated patch, should we make a similar change in
> AlterPublicationTables Function header to mention Set too:
> /*
> * Add or remove table to/from publication.
> */
> static void
> AlterPublicationTables(AlterPublicationStmt *stmt, HeapTuple tup,
> List *tables, List *schemaidlist)
> 

Sorry for the late reply.

I am not sure if we need this change because the way to SET the tables in
publication is that drop tables and then add tables, instead of directly
replacing the list of tables in the publication. (We can see this point in
AlterPublicationTables function.). Thoughts?

Regards,
Tang

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Patch to avoid orphaned dependencies
Next
From: Bharath Rupireddy
Date:
Subject: Re: skip replication slot snapshot/map file removal during end-of-recovery checkpoint