1
1
<!--
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 $
3
3
-->
4
4
5
5
<Chapter Id="runtime">
@@ -1994,7 +1994,8 @@ SET ENABLE_SEQSCAN TO OFF;
1994
1994
<para>
1995
1995
Causes the duration of every completed statement to be logged.
1996
1996
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
1998
1999
can link the statement to the duration using the process
1999
2000
ID. The default is off. Only superusers can turn off this
2000
2001
option if it is enabled by the administrator.
@@ -2015,6 +2016,8 @@ SET ENABLE_SEQSCAN TO OFF;
2015
2016
processes without controlling sessions. <application>Syslog</> produces its own
2016
2017
timestamp and process ID information, so you probably do not want to
2017
2018
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.
2018
2021
<informaltable>
2019
2022
<tgroup cols="3">
2020
2023
<thead>
@@ -2059,7 +2062,8 @@ SET ENABLE_SEQSCAN TO OFF;
2059
2062
<row>
2060
2063
<entry><literal>%c</literal></entry>
2061
2064
<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
2063
2067
are the Session Start Time and the Process ID, so this can also
2064
2068
be used as a space saving way of printing these items.</entry>
2065
2069
<entry>Yes</entry>
@@ -2094,19 +2098,6 @@ SET ENABLE_SEQSCAN TO OFF;
2094
2098
</listitem>
2095
2099
</varlistentry>
2096
2100
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
-
2110
2101
<varlistentry id="guc-log-statement" xreflabel="log_statement">
2111
2102
<term><varname>log_statement</varname> (<type>boolean</type>)</term>
2112
2103
<listitem>
@@ -2121,16 +2112,6 @@ SET ENABLE_SEQSCAN TO OFF;
2121
2112
</listitem>
2122
2113
</varlistentry>
2123
2114
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
-
2134
2115
<varlistentry id="guc-log-hostname" xreflabel="log_hostname">
2135
2116
<term><varname>log_hostname</varname> (<type>boolean</type>)</term>
2136
2117
<listitem>
@@ -2144,19 +2125,6 @@ SET ENABLE_SEQSCAN TO OFF;
2144
2125
</listitem>
2145
2126
</varlistentry>
2146
2127
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
-
2160
2128
</variablelist>
2161
2129
</sect3>
2162
2130
</sect2>