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 455280adbad38676c440c928592f75989a594d23..c00e63ed9626c38739ee79db5bdb9fb8db3b2a74 100644 (file)
--- 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>