| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Ryan Murphy <ryanfmurphy(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Clarifying "server starting" messaging in pg_ctl start without --wait |
| Date: | 2016-12-23 22:33:24 |
| Message-ID: | CAB7nPqTJiuSxxT_vWhLdxMURmrVDBiS_E+g6sGfY_mLF9quXHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 23, 2016 at 10:47 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2016-12-23 22:44:18 | Re: Incautious handling of overlength identifiers |
| Previous Message | Fabien COELHO | 2016-12-23 22:24:58 | Re: proposal: session server side variables |