Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.

From: Shubham Khanna <khannashubham1197(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.
Date: 2025-03-19 05:13:48
Message-ID: CAHv8RjK3WQPBJk15qbGjLjHKxVT=X8m+hhWZj77iyA0PTxUXxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 19, 2025 at 9:06 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Wed, Mar 19, 2025 at 2:11 AM David G. Johnston
> <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> >
> > On Tue, Mar 18, 2025 at 4:47 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >>
> >> I don't understand --dry-run part of conversation here. As per
> >> existing code (or with the patch), we seem to be already printing the
> >> publications to be dropped in dry-run mode.
> >
> >
> > Sorry, that was me making a bad assumption rather than checking first.
> >
> >
> > I'm still bothered by the last paragraph of the commit message saying to backup these publications when the preceding one claims strongly and unconditionally that they are redundant and serve no purpose.
> >
>
> Agreed. I suggest we remove that part of the paragraph (Users should
> back up any manually created publications before running this command.
> By default, publications are preserved to avoid unintended data loss.)
> from the commit message.
>

I have updated the commit message according to the suggestions. The
part about backing up manually created publications has been removed
to align with the statement that they are redundant and serve no
purpose.

The attached patch at [1] contains the suggested changes.

[1] - https://www.postgresql.org/message-id/CAHv8RjJNE1ZvWhsgL54iPsJhomhcG%2B-SGPN8AnnwdLmWt6A44A%40mail.gmail.com

Thanks and regards,
Shubham Khanna.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-03-19 05:15:11 Re: Proposal - Allow extensions to set a Plan Identifier
Previous Message Masahiko Sawada 2025-03-19 05:12:48 Re: Separate GUC for replication origins