11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.249 2004/03/12 00 :56:00 neilc Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.250 2004/03/15 15 :56:21 momjian Exp $
33-->
44
55<Chapter Id="runtime">
@@ -1994,7 +1994,8 @@ SET ENABLE_SEQSCAN TO OFF;
19941994 <para>
19951995 Causes the duration of every completed statement to be logged.
19961996 To use this option, it is recommended that you also enable
1997- <varname>log_statement</> and <varname>log_pid</> so that you
1997+ <varname>log_statement</> and if not using <application>syslog</>
1998+ log the PID using <varname>log_line_prefix</> so that you
19981999 can link the statement to the duration using the process
19992000 ID. The default is off. Only superusers can turn off this
20002001 option if it is enabled by the administrator.
@@ -2015,6 +2016,8 @@ SET ENABLE_SEQSCAN TO OFF;
20152016 processes without controlling sessions. <application>Syslog</> produces its own
20162017 timestamp and process ID information, so you probably do not want to
20172018 use those escapes if you are using <application>syslog</>.
2019+ This option can only be set at server start or in the
2020+ <filename>postgresql.conf</filename> configuration file.
20182021 <informaltable>
20192022 <tgroup cols="3">
20202023 <thead>
@@ -2059,7 +2062,8 @@ SET ENABLE_SEQSCAN TO OFF;
20592062 <row>
20602063 <entry><literal>%c</literal></entry>
20612064 <entry>Session ID. A unique identifier for each session.
2062- It is 2 4-byte hexadecimal numbers separated by a dot. The numbers
2065+ It is 2 4-byte hexadecimal numbers (without leading zeros)
2066+ separated by a dot. The numbers
20632067 are the Session Start Time and the Process ID, so this can also
20642068 be used as a space saving way of printing these items.</entry>
20652069 <entry>Yes</entry>
@@ -2094,19 +2098,6 @@ SET ENABLE_SEQSCAN TO OFF;
20942098 </listitem>
20952099 </varlistentry>
20962100
2097- <varlistentry>
2098- <term><varname>log_pid</varname> (<type>boolean</type>)</term>
2099- <listitem>
2100- <para>
2101- Prefixes each message in the server log file with the process ID of
2102- the server process. This is useful to sort out which messages
2103- pertain to which connection. The default is off. This parameter
2104- does not affect messages logged via <application>syslog</>, which
2105- always contain the process ID.
2106- </para>
2107- </listitem>
2108- </varlistentry>
2109-
21102101 <varlistentry id="guc-log-statement" xreflabel="log_statement">
21112102 <term><varname>log_statement</varname> (<type>boolean</type>)</term>
21122103 <listitem>
@@ -2121,16 +2112,6 @@ SET ENABLE_SEQSCAN TO OFF;
21212112 </listitem>
21222113 </varlistentry>
21232114
2124- <varlistentry id="guc-log-timestamp" xreflabel="log_timestamp">
2125- <term><varname>log_timestamp</varname> (<type>boolean</type>)</term>
2126- <listitem>
2127- <para>
2128- Prefixes each server log message with a time stamp. The default
2129- is off.
2130- </para>
2131- </listitem>
2132- </varlistentry>
2133-
21342115 <varlistentry id="guc-log-hostname" xreflabel="log_hostname">
21352116 <term><varname>log_hostname</varname> (<type>boolean</type>)</term>
21362117 <listitem>
@@ -2144,19 +2125,6 @@ SET ENABLE_SEQSCAN TO OFF;
21442125 </listitem>
21452126 </varlistentry>
21462127
2147- <varlistentry id="guc-log-source-port" xreflabel="log_source_port">
2148- <term><varname>log_source_port</varname> (<type>boolean</type>)</term>
2149- <listitem>
2150- <para>
2151- Shows the outgoing port number of the connecting host in the
2152- connection log messages. You could trace back the port number
2153- to find out what user initiated the connection. Other than
2154- that, it's pretty useless and therefore off by default. This
2155- option can only be set at server start.
2156- </para>
2157- </listitem>
2158- </varlistentry>
2159-
21602128 </variablelist>
21612129 </sect3>
21622130 </sect2>