Feedback-ID: ie3de48e3:Fastmail
Date: Tue, 18 Nov 2025 16:39:05 +0100
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Peter Smith <smithpb2250@gmail.com>
Cc: Chao Li <li.evan.chao@gmail.com>, Euler Taveira <euler@eulerto.com>,
	"kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: pg_createsubscriber --dry-run logging concerns
Message-ID: <202511181536.oemmhqgh7f27@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAHut+PssSBRmrWLuBQ=gu1PdnefAB29CeC3nmYUDdF=eWFtfUg@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202511181536.oemmhqgh7f27%40alvherre.pgsql>
Precedence: bulk

On 2025-Nov-12, Peter Smith wrote:

> It is tempting to implement a "--silent" mode, but if I did that, I
> would then feel obliged to document and test it. I don't want to go
> further down this rabbit hole for what was originally supposed to be
> trivial logging.

Yeah, I understand.

> So, I am calling it quits for this 0001 patch.
> 
> Perhaps it's still of some use to push changes for everything except
> the pg_resetwal? Or if you prefer to just abandon the whole patch,
> that is OK too. Thanks for trying.

Got it.  I pushed it for the other programs and marked the CF entry as
committed -- thanks for the patches and the discussion.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"I'm impressed how quickly you are fixing this obscure issue. I came from 
MS SQL and it would be hard for me to put into words how much of a better job
you all are doing on [PostgreSQL]."
 Steve Midgley, http://archives.postgresql.org/pgsql-sql/2008-08/msg00000.php