Re: pg_createsubscriber --dry-run logging concerns

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, 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>, "L(dot) pgsql-hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_createsubscriber --dry-run logging concerns
Date: 2026-07-01 08:21:50
Message-ID: 76d5fc86-aeb0-4841-9f24-1177529eed8f@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 29.06.26 23:13, Álvaro Herrera wrote:
> On 2026-06-29, 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?
>
> Yeah, that works for me. It makes me wonder what was I thinking when I requested that newline.

Ok, done.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shlok Kyal 2026-07-01 08:30:06 Re: Support EXCEPT for ALL SEQUENCES publications
Previous Message Ewan Young 2026-07-01 08:20:39 Re: Prevent crash when calling pgstat functions with unregistered stats kind