| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Ryan Murphy <ryanfmurphy(at)gmail(dot)com>, Beena Emerson <memissemerson(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait |
| Date: | 2017-01-19 14:55:35 |
| Message-ID: | c6236fca-62e6-a3c3-8367-8e426abe74b2@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/18/17 3:47 PM, Robert Haas wrote:
> Anybody who has got a script that runs pg_ctl unattended mode likely
> now has to go update that script to add --no-wait.
The state of init scripts and other start scripts out there is such a
mess, it's hard to make general statements like this. Many start
scripts still start the postmaster directly and have confusing or
outdated advice about whether or not to use pg_ctl. Some implement
their own waiting logic after starting. Some just ignore the issue and
do wrong or inconsistent things.
With this change, together with the systemd support that is already out
there with 9.6, and with the new promote wait support, we'll at least
have a consistent approach going forward and have a better shot at
sorting out the current mess.
Someone who really wants the old behavior can add the command-line
option in a backward-compatible way.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-01-19 14:57:23 | Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait |
| Previous Message | Stephen Frost | 2017-01-19 14:53:46 | Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait |