database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-25 21:42:33 +03:00
Code

Remove tabs from SGML files.

Browse Source
This commit is contained in:
Bruce Momjian 2007-08-21 15:13:16 +00:00
parent b913a94d0a
commit bbde090330
1 changed files with 22 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
doc/src/sgml/config.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.139 2007/08/19 03:23:30 adunstan Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.140 2007/08/21 15:13:16 momjian Exp $ -->
<chapter Id="runtime-config"> <chapter Id="runtime-config">
<title>Server Configuration</title> <title>Server Configuration</title>
@ -2287,7 +2287,7 @@ SELECT * FROM parent WHERE key = 2400;
<listitem> <listitem>
<para> <para>
This parameter allows messages sent to <application>stderr</>, This parameter allows messages sent to <application>stderr</>,
and CSV logs, to be and CSV logs, to be
captured and redirected into log files. captured and redirected into log files.
This method, in combination with logging to <application>stderr</>, This method, in combination with logging to <application>stderr</>,
is often more useful than is often more useful than
@ -2295,8 +2295,8 @@ SELECT * FROM parent WHERE key = 2400;
might not appear in <application>syslog</> output (a common example might not appear in <application>syslog</> output (a common example
is dynamic-linker failure messages). is dynamic-linker failure messages).
This parameter can only be set at server start. This parameter can only be set at server start.
<varname>logging_collector</varname> must be enabled to generate <varname>logging_collector</varname> must be enabled to generate
CSV logs. CSV logs.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -2342,11 +2342,11 @@ SELECT * FROM parent WHERE key = 2400;
file or on the server command line. file or on the server command line.
</para> </para>
<para> <para>
If <varname>log_destination</> is set to <systemitem>csvlog</>, If <varname>log_destination</> is set to <systemitem>csvlog</>,
<literal>.csv</> will be appended to the timestamped <literal>.csv</> will be appended to the timestamped
<varname>log_filename</> to create the final log file name. <varname>log_filename</> to create the final log file name.
(If log_filename ends in <literal>.log</>, the suffix is overwritten.) (If log_filename ends in <literal>.log</>, the suffix is overwritten.)
In the case of the example above, the In the case of the example above, the
file name will be <literal>server_log.1093827753.csv</literal> file name will be <literal>server_log.1093827753.csv</literal>
</para> </para>
</listitem> </listitem>
@ -3088,9 +3088,9 @@ SELECT * FROM parent WHERE key = 2400;
<title>Using the csvlog</title> <title>Using the csvlog</title>
<para> <para>
Including <literal>csvlog</> in the <varname>log_destination</> list Including <literal>csvlog</> in the <varname>log_destination</> list
provides a convenient way to import log files into a database table. provides a convenient way to import log files into a database table.
Here is a sample table definition for storing csvlog output: Here is a sample table definition for storing csvlog output:
</para> </para>
<programlisting> <programlisting>
@ -3124,7 +3124,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
<para> <para>
There are a few things you need to import csvlog files easily and There are a few things you need to import csvlog files easily and
automatically: automatically:
<orderedlist> <orderedlist>
<listitem> <listitem>
@ -3141,15 +3141,15 @@ guess what
<listitem> <listitem>
<para> <para>
Set <varname>log_rotation_size</varname> to 0 to disable Set <varname>log_rotation_size</varname> to 0 to disable
size-based log rotation, as it makes the log filename difficult size-based log rotation, as it makes the log filename difficult
to predict. to predict.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Set <varname>log_truncate_on_rotate</varname> = on so that old Set <varname>log_truncate_on_rotate</varname> = on so that old
log data isn't mixed with the new in the same file. log data isn't mixed with the new in the same file.
</para> </para>
</listitem> </listitem>
@ -3160,12 +3160,12 @@ guess what
the same information twice. The COPY command commits all of the same information twice. The COPY command commits all of
the data it imports at one time, and any single error will the data it imports at one time, and any single error will
cause the entire import to fail. cause the entire import to fail.
If you import a partial log file and later import the file again If you import a partial log file and later import the file again
when it is complete, the primary key violation will cause the when it is complete, the primary key violation will cause the
import to fail. Wait until the log is complete and closed before import to fail. Wait until the log is complete and closed before
import. This will also protect against accidently importing a import. This will also protect against accidently importing a
partial line that hasn't been completely written, which would partial line that hasn't been completely written, which would
also cause the COPY to fail. also cause the COPY to fail.
</para> </para>
</listitem> </listitem>
</orderedlist> </orderedlist>