Re: pg_createsubscriber --dry-run logging concerns

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: Euler Taveira <euler(at)eulerto(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Chao Li <li(dot)evan(dot)chao(at)gmail(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: 2026-06-29 20:21:39
Message-ID: CAHut+PsyOcRAaFh5o0CWyFWLfrAaeVji=OKGjKO2RjH1P+qaiw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 30, 2026 at 8:15 AM Euler Taveira <euler(at)eulerto(dot)com> wrote:
>
> On Mon, Jun 29, 2026, at 10:56 AM, Peter Eisentraut wrote:
> >
> > I have a follow-up for this. Earlier in this thread it was asked to
> > combine the dry-run info message into one string with a newline. But I
> > think this doesn't really fit the message style guidelines. I suggest
> > to use a primary plus detail style here too. How about the attached patch?
> >
>
> LGTM.
>

Ditto.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-06-29 20:22:06 Re: PostgreSQL select-only CTE removal is too aggressive?
Previous Message Euler Taveira 2026-06-29 20:14:41 Re: pg_createsubscriber --dry-run logging concerns