| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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-18 01:35:01 |
| Message-ID: | CAB7nPqS2YnF9dnJRxBZRPOyNRToteY1oNtn_Z+-ArG1F0RYEog@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 18, 2017 at 7:31 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Perhaps we need a way for pg_ctl to realize a cold-standby case and
> throw an error or warning if --wait is specified then, but that hardly
> seems like the common use-case. It also wouldn't make any sense to have
> anything in the init system which depended on PG being up in such a case
> because, well, PG isn't ever going to be 'up'.
Yeah, it seems to me that we are likely looking for a wait mode saying
to exit pg_ctl once Postgres is happily rejecting connections, because
that means that it is up and that it is sorting out something first
before accepting them. This would basically filter the states in the
control file that we find as acceptable if the connection test
continues complaining about PQPING_REJECT.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-01-18 01:37:34 | Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait |
| Previous Message | Haribabu Kommi | 2017-01-18 00:55:47 | Re: Parallel Index Scans |