Re: Clarifying "server starting" messaging in pg_ctl start without --wait

From: Ryan Murphy <ryanfmurphy(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Clarifying "server starting" messaging in pg_ctl start without --wait
Date: 2017-01-02 18:14:34
Message-ID: CAHeEsBeZnHVh-dSAuem4m7x8gFYoxajKkKLVTTtNV+RLz32AKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Making --wait the default may or may not be sensible -- I'm not sure
> -- but removing --no-wait is clearly a bad idea, and we shouldn't do
> it. The fact that the problems created by removing it might be
> solvable doesn't mean that it's a good idea to create them in the
> first place.
>
>
>
I agree with Robert - pg_ctl is no doubt used in all kinds of scripts that
would then have to change.
It may make sense to have --wait be the default though - certainly less
confusing to new users!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-01-02 18:18:29 Re: Compiler warnings
Previous Message Robert Haas 2017-01-02 18:09:57 Re: Clarifying "server starting" messaging in pg_ctl start without --wait