Re: pg_createsubscriber --dry-run logging concerns

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_createsubscriber --dry-run logging concerns
Date: 2025-11-18 15:39:05
Message-ID: 202511181536.oemmhqgh7f27@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-11-18 15:40:41 Re: Performance issues with parallelism and LIMIT
Previous Message Nathan Bossart 2025-11-18 15:31:35 Re: [PATCH] Add hints for invalid binary encoding names in encode/decode functions