Skip site navigation (1) Skip section navigation (2)

Re: Obsolete description in pg_ctl-ref.sgml

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Obsolete description in pg_ctl-ref.sgml
Date: 2010-12-14 21:35:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
On Sun, Dec 12, 2010 at 11:21 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Sat, Dec 11, 2010 at 1:27 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>>> Notes
>>>> Waiting for complete startup is not a well-defined operation and
>>>> might fail if access control is set up so that a local client cannot
>>>> connect without manual interaction (e.g., password authentication).
>>>> For additional connection variables, see Section 31.13, and for
>>>> passwords, also see Section 31.14.
>>> The above also seems to be obsolete, thanks to recently-introduced
>>> PQping. Can we remove that?
>> Should we remove only the first sentence and keep the second one, or
>> is it more appropriate to remove the whole thing?
> At least the reference to section 31.14 is needless since password
> authentication doesn't affect the pg_ctl -w for now. But, on the second
> thought, it can still fail because of miss-configuration of connection
> variable, for example PGHOST.

I thought PQping() was supposed to handle that correctly.  There are
PQPING_NO_ATTEMPT.  I believe the last is intended to cover blatant
misconfiguration.  Or maybe I'm not understanding what you're
referring to.

Robert Haas
The Enterprise PostgreSQL Company

In response to


pgsql-docs by date

Next:From: Robert HaasDate: 2010-12-14 22:02:38
Subject: Re: Is timestamptz alias documented?
Previous:From: Fujii MasaoDate: 2010-12-13 04:21:51
Subject: Re: Obsolete description in pg_ctl-ref.sgml

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group