From: Robert Haas <rhaas@postgresql.org>
Date: Fri, 17 Dec 2010 01:57:33 +0000 (-0500)
Subject: Waiting for complete startup is now a well-defined operation.
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=df142bf82c84de5d0588ae7d52881501abb039ed;p=users%2Fhanada%2Fpostgres.git

Waiting for complete startup is now a well-defined operation.

Per report from Fujii Masao, and subsequent discussion.
---

diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml
index 455280adba..c00e63ed96 100644
--- a/doc/src/sgml/ref/pg_ctl-ref.sgml
+++ b/doc/src/sgml/ref/pg_ctl-ref.sgml
@@ -522,19 +522,6 @@ PostgreSQL documentation
  </refsect1>
 
 
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   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 <xref linkend="libpq-envars">,
-   and for passwords, also see <xref linkend="libpq-pgpass">.
-  </para>
- </refsect1>
-
-
  <refsect1 id="R1-APP-PGCTL-2">
   <title>Examples</title>