11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.291 2004/11/05 19:15:49 tgl Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.292 2004/11/14 19:35:28 tgl Exp $
33-->
44
55<Chapter Id="runtime">
@@ -2150,7 +2150,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32
21502150 to the log. The default is <literal>NOTICE</>. Note that
21512151 <literal>LOG</> has a different rank here than in
21522152 <varname>client_min_messages</>.
2153- Only superusers canincrease thisoption .
2153+ Only superusers canchange thissetting .
21542154 </para>
21552155 </listitem>
21562156 </varlistentry>
@@ -2186,7 +2186,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32
21862186 SQL statements causing errors, fatal errors, or panics will be
21872187 logged. Enabling this option can be helpful in tracking down
21882188 the source of any errors that appear in the server log.
2189- Only superusers canincrease thisoption .
2189+ Only superusers canchange thissetting .
21902190 </para>
21912191 </listitem>
21922192 </varlistentry>
@@ -2204,8 +2204,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32
22042204 <literal>250</literal> then all SQL statements that run 250ms
22052205 or longer will be logged. Enabling this option can be
22062206 useful in tracking down unoptimized queries in your applications.
2207- Only superusers can increase this or set it to minus-one if this
2208- option is set by the administrator.
2207+ Only superusers can change this setting.
22092208 </para>
22102209 </listitem>
22112210 </varlistentry>
@@ -2332,7 +2331,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32
23322331 these displays to produce a more readable but much longer
23332332 output format. <varname>client_min_messages</varname> or
23342333 <varname>log_min_messages</varname> must be
2335- <literal>DEBUG1</literal> or lower to send output to the
2334+ <literal>DEBUG1</literal> or lower to sendthe output to the
23362335 client or server logs. These options are off by default.
23372336 </para>
23382337 </listitem>
@@ -2372,10 +2371,9 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32
23722371 <varname>log_statement</> to be logged. When using this option,
23732372 if you are not using <application>syslog</>, it is recommended
23742373 that you log the PID or session ID using <varname>log_line_prefix</>
2375- or log the session ID so that you can link the statement to the
2374+ so that you can link the statement to the
23762375 duration using the process ID or session ID. The default is off.
2377- Only superusers can turn off this option if it is enabled by the
2378- administrator.
2376+ Only superusers can change this setting.
23792377 </para>
23802378 </listitem>
23812379 </varlistentry>
@@ -2487,35 +2485,35 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32
24872485 <listitem>
24882486 <para>
24892487 Controls which SQL statements are logged. Valid values are
2490- <literal>all </>, <literal>ddl</>, <literal>mod</>, and
2491- <literal>none </>. <literal>ddl</> logs all data definition
2488+ <literal>none </>, <literal>ddl</>, <literal>mod</>, and
2489+ <literal>all </>. <literal>ddl</> logs all data definition
24922490 commands like <literal>CREATE</>, <literal>ALTER</>, and
24932491 <literal>DROP</> commands. <literal>mod</> logs all
24942492 <literal>ddl</> statements, plus <literal>INSERT</>,
24952493 <literal>UPDATE</>, <literal>DELETE</>, <literal>TRUNCATE</>,
24962494 and <literal>COPY FROM</>. <literal>PREPARE</> and
2497- <literal>EXPLAIN ANALYZE</> statements are alsoconsidered for
2498- appropriatecommands.
2495+ <literal>EXPLAIN ANALYZE</> statements are alsologged if their
2496+ contained command is of an appropriatetype.
24992497 </para>
25002498 <para>
2501- The default is <literal>none</>. Only superusers canreduce
2502- the detail of this option if it has been set by an administrator .
2499+ The default is <literal>none</>. Only superusers canchange this
2500+ setting .
25032501 </para>
25042502
25052503 <note>
25062504 <para>
2507- The <command>EXECUTE</command> statement not considered a
2505+ The <command>EXECUTE</command> statementis not considered a
25082506 <literal>ddl</> or <literal>mod</> statement. When it is logged,
25092507 only the name of the prepared statement is reported, not the
25102508 actual prepared statement.
25112509 </para>
25122510
25132511 <para>
2514- When a function is defined ina server-side language like
2515- <application>PL/pgSQL</application>, any queries executed by
2516- the function will only be logged the first time that the
2512+ When a function is defined inthe
2513+ <application>PL/pgSQL</application>server-side language , any queries
2514+ executed by the function will only be logged the first time that the
25172515 function is invoked in a particular session. This is because
2518- the <application>PL/pgSQL</application> keeps a cache of the
2516+ <application>PL/pgSQL</application> keeps a cache of the
25192517 query plans produced for the SQL statements in the function.
25202518 </para>
25212519 </note>
@@ -2556,11 +2554,10 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32
25562554 For each query, write performance statistics of the respective
25572555 module to the server log. This is a crude profiling
25582556 instrument. <varname>log_statement_stats</varname> reports total
2559- statement statistics, while the others report per-state statistics.
2560- <varname>log_statement_stats</varname> can not be enabled with
2561- the other options. All of these options are disabled by default.
2562- Only superusers can turn off any of these options if they have
2563- been enabled by the administrator.
2557+ statement statistics, while the others report per-module statistics.
2558+ <varname>log_statement_stats</varname> cannot be enabled together with
2559+ any of the per-module options. All of these options are disabled by
2560+ default. Only superusers can change these settings.
25642561 </para>
25652562 </listitem>
25662563 </varlistentry>