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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-20 21:37:04
Message-ID: 98628509-6e14-9af5-d46b-0d3d7c08d17e@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/20/16 3:49 PM, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> Maybe the fix is to make --wait the default?
> I was wondering about that too ... does anyone remember the rationale
> for the current behavior?

Probably because that didn't work reliably before pg_ctl learned how to
get the right port number and PQping() and such things.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-12-20 22:53:08 Re: Parallel tuplesort (for parallel B-Tree index creation)
Previous Message Michael Paquier 2016-12-20 21:30:49 Re: pg_authid.rolpassword format (was Re: Password identifiers, protocol aging and SCRAM protocol)