-->
<refentry id="app-pg-ctl">
+ <indexterm zone="app-pg-ctl">
+ <primary>pg_ctl</primary>
+ </indexterm>
+
<refmeta>
<refentrytitle><application>pg_ctl</application></refentrytitle>
<manvolnum>1</manvolnum>
<refpurpose>initialize, start, stop, or control a <productname>PostgreSQL</productname> server</refpurpose>
</refnamediv>
- <indexterm zone="app-pg-ctl">
- <primary>pg_ctl</primary>
- </indexterm>
-
<refsynopsisdiv>
<cmdsynopsis>
<command>pg_ctl</command>
the specified data directory. If it is, the <acronym>PID</acronym>
and the command line options that were used to invoke it are
displayed. If the server is not running, the process returns an
- exit status of 3.
+ exit status of 3. If an accessible data directory is not specified,
+ the process returns an exit status of 4.
</para>
<para>
<title>Options for Windows</title>
<variablelist>
+ <varlistentry>
+ <term><option>-e <replaceable class="parameter">source</replaceable></option></term>
+ <listitem>
+ <para>
+ Name of the event source for <application>pg_ctl</application> to use
+ for logging to the event log when running as a Windows service. The
+ default is <literal>PostgreSQL</literal>. Note that this only controls
+ the logging from <application>pg_ctl</application> itself - once
+ started, the server will use the event source specified
+ by <xref linkend="guc-event-source">. Should the server fail during
+ early startup, it may also log using the default event
+ source <literal>PostgreSQL</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><option>-N <replaceable class="parameter">servicename</replaceable></option></term>
<listitem>