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

From Peter Eisentraut
Subject Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Date
Msg-id 455845d1-441d-cc40-d2a7-b47f4e422489@2ndquadrant.com
Whole thread Raw
In response to Re: Prevent printing "next step instructions" in initdb and pg_upgrade  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Prevent printing "next step instructions" in initdb and pg_upgrade  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On 2021-01-17 14:38, Magnus Hagander wrote:
> On Thu, Jan 7, 2021 at 11:53 AM Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com> wrote:
>>
>> After pondering this again, I think we can go with initdb
>> --no-instructions, as in your patch.
>>
>> As a minor nitpick, I would leave out the
>>
>>       else
>>           printf(_("\nSuccess.\n"));
>>
>> in the --no-instructions case.
> 
> OK, thanks. I have applied it as such, with that message moved inside
> the if statement.

It appears that there is an extra blank line in the initdb output before 
"Success" now.

-- 
Peter Eisentraut
2ndQuadrant, an EDB company
https://www.2ndquadrant.com/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Can we have a new SQL callable function to get Postmaster PID?
Next
From: Peter Eisentraut
Date:
Subject: Re: Dumping/restoring fails on inherited generated column