mirror of
https://github.com/postgres/postgres.git
synced 2025-07-31 22:04:40 +03:00
Add option to pg_ctl to choose event source for logging
pg_ctl will log to the Windows event log when it is running as a service, which is the primary way of running PostgreSQL on Windows. This option makes it possible to specify which event source to use for this, in order to separate different instances. The server logging itself is still controlled by the regular logging parameters, including a separate setting for the event source. The parameter to pg_ctl only controlls the logging from pg_ctl itself. MauMau, review in many iterations by Amit Kapila and me.
This commit is contained in:
@ -419,6 +419,22 @@ PostgreSQL documentation
|
||||
<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>
|
||||
|
Reference in New Issue
Block a user