Re: Prevent printing "next step instructions" in initdb and pg_upgrade - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Date
Msg-id 703378.1612806961@sss.pgh.pa.us
Whole thread Raw
In response to Re: Prevent printing "next step instructions" in initdb and pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> Bruce Momjian <bruce@momjian.us> writes:
>> On Sun, Feb  7, 2021 at 11:21:05AM +0100, Magnus Hagander wrote:
>>> Isn't the whole "Success." at the end redundant here, and we should
>>> just end the message after the pg_ctl command? So not just the extra
>>> newline, but the whole thing?

>> Agreed.

> +1

In fact, I just noticed that none of our back branches print that
extra "Success." either.  So that's a bug, is what it is.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: pg_replication_origin_drop API potential race condition
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_replication_origin_drop API potential race condition