Re: [HACKERS] Clarifying "server starting" messaging in pg_ctl startwithout --wait - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Clarifying "server starting" messaging in pg_ctl startwithout --wait
Date
Msg-id 98628509-6e14-9af5-d46b-0d3d7c08d17e@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Clarifying "server starting" messaging in pg_ctl start without --wait  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 12/20/16 3:49 PM, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_authid.rolpassword format (was Re: [HACKERS] Passwordidentifiers, protocol aging and SCRAM protocol)
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)