I have added additional documentation for environment variables for
pg_ctl, patch attached.
---------------------------------------------------------------------------
Marvin Solomon wrote:
>
> [This is meant to be a follow-up of a bug report I sent earlier using the web
> form. It's not clear to me the right way to post a follow-up, since I didn't
> get a copy of the email generated by the web form, and the email hasn't shown
> up on the pgsql-bugs web site -- at least not yet.]
>
> I subsequently discovered that setting PGUSER in the environment gets around
> the first problem I mentioned, so it's really just a documentation problem:
> PGUSER is not mentioned on the pg_ctl doc page.
>
> But I found a worse problem. Sometimes (not repeatably), pg_ctl start -w
> logs the message
>
> FATAL: the database is starting up
>
> and immediately returns. I believe the correct thing for it to do when it
> gets this message from an attempt to open a session is to try again. Instead,
> it returns as if the startup was successful.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/ref/pg_ctl-ref.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v
retrieving revision 1.36
diff -c -c -r1.36 pg_ctl-ref.sgml
*** doc/src/sgml/ref/pg_ctl-ref.sgml 5 Jan 2007 16:17:54 -0000 1.36
--- doc/src/sgml/ref/pg_ctl-ref.sgml 11 Jan 2007 02:28:00 -0000
***************
*** 356,362 ****
</variablelist>
<para>
! For others, see <xref linkend="app-postgres">.
</para>
</refsect1>
--- 356,362 ----
</variablelist>
<para>
! For additional server variables, see <xref linkend="app-postgres">.
</para>
</refsect1>
***************
*** 427,433 ****
<para>
Waiting for complete start is not a well-defined operation and may
fail if access control is set up so that a local client cannot
! connect without manual interaction (e.g., password authentication).
</para>
</refsect1>
--- 427,435 ----
<para>
Waiting for complete start is not a well-defined operation and may
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>
