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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: 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 20:37:23
Message-ID: CA+TgmoZd0D0q_Nz8xmKiNtTfOVVRn9ayYDYhGU96cbDrxqyT3Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 17, 2017 at 5:31 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> If I'm understanding your concern correctly, you're worried about the
> case of a cold standby where the database is only replaying WAL but not
> configured to come up as a hot standby and therefore PQping() won't ever
> succeed?

I think we've changed the defaults to make things better for an
attended startup and worse for an unattended startup. But I think
most PostgreSQL startups are probably unattended.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2017-01-18 20:42:06 Re: jsonb_delete with arrays
Previous Message Robert Haas 2017-01-18 20:29:25 Re: Declarative partitioning - another take