Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility. - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.
Date
Msg-id CAA4eK1JHGJ=Z0ghQMAyxD7jO84Y7Ab-uwcOfid3NvBNxr377kA@mail.gmail.com
Whole thread Raw
In response to Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.
List pgsql-hackers
On Wed, Mar 19, 2025 at 2:11 AM David G. Johnston
<david.g.johnston@gmail.com> wrote:
>
> On Tue, Mar 18, 2025 at 4:47 AM Amit Kapila <amit.kapila16@gmail.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
oneclaims 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.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: making EXPLAIN extensible
Next
From: Sungwoo Chang
Date:
Subject: Re: like pg_shmem_allocations, but fine-grained for DSM registry ?