Re: [HACKERS] Clarifying "server starting" messaging in pg_ctl startwithout --wait - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Clarifying "server starting" messaging in pg_ctl startwithout --wait
Date
Msg-id CAB7nPqTJiuSxxT_vWhLdxMURmrVDBiS_E+g6sGfY_mLF9quXHA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Clarifying "server starting" messaging in pg_ctl startwithout --wait  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Clarifying "server starting" messaging in pg_ctl start without --wait  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Dec 23, 2016 at 10:47 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 12/20/16 3:43 PM, Peter Eisentraut wrote:
>> On 12/20/16 3:31 PM, Ryan Murphy wrote:
>>> I'm concerned some new users may not understand this behavior of pg_ctl,
>>> so I wanted to suggest that we add some additional messaging after
>>> "server starting" - something like:
>>>
>>> $ pg_ctl -D datadir -l logfile start
>>> server starting
>>> (to wait for confirmation that server actually started, try pg_ctl again
>>> with --wait)
>>
>> Maybe the fix is to make --wait the default?
>
> Here is a patch for that.

Is there still a use case for --no-wait in the real world? Why not
simply ripping it out?
-- 
Michael



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] proposal: session server side variables
Next
From: Joe Conway
Date:
Subject: Re: [HACKERS] Incautious handling of overlength identifiers