Re: pg_createsubscriber --dry-run logging concerns

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: "Peter Eisentraut" <peter(at)eisentraut(dot)org>, "Peter Smith" <smithpb2250(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: "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:14:41
Message-ID: eadcb333-6724-4584-8f10-52a1bf756a39@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Euler Taveira
EDB https://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-06-29 20:21:39 Re: pg_createsubscriber --dry-run logging concerns
Previous Message Kirill Reshke 2026-06-29 19:58:15 Re: PostgreSQL select-only CTE removal is too aggressive?