Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitbbde090

Browse files
committed
Remove tabs from SGML files.
1 parentb913a94 commitbbde090

File tree

1 file changed

+22
-22
lines changed

1 file changed

+22
-22
lines changed

‎doc/src/sgml/config.sgml‎

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.139 2007/08/19 03:23:30 adunstan Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.140 2007/08/21 15:13:16 momjian Exp $ -->
22

33
<chapter Id="runtime-config">
44
<title>Server Configuration</title>
@@ -2287,16 +2287,16 @@ SELECT * FROM parent WHERE key = 2400;
22872287
<listitem>
22882288
<para>
22892289
This parameter allows messages sent to <application>stderr</>,
2290-
and CSV logs, to be
2290+
and CSV logs, to be
22912291
captured and redirected into log files.
22922292
This method, in combination with logging to <application>stderr</>,
22932293
is often more useful than
22942294
logging to <application>syslog</>, since some types of messages
22952295
might not appear in <application>syslog</> output (a common example
22962296
is dynamic-linker failure messages).
22972297
This parameter can only be set at server start.
2298-
<varname>logging_collector</varname> must be enabled to generate
2299-
CSV logs.
2298+
<varname>logging_collector</varname> must be enabled to generate
2299+
CSV logs.
23002300
</para>
23012301
</listitem>
23022302
</varlistentry>
@@ -2342,11 +2342,11 @@ SELECT * FROM parent WHERE key = 2400;
23422342
file or on the server command line.
23432343
</para>
23442344
<para>
2345-
If <varname>log_destination</> is set to <systemitem>csvlog</>,
2346-
<literal>.csv</> will be appended to the timestamped
2347-
<varname>log_filename</> to create the final log file name.
2348-
(If log_filename ends in <literal>.log</>, the suffix is overwritten.)
2349-
In the case of the example above, the
2345+
If <varname>log_destination</> is set to <systemitem>csvlog</>,
2346+
<literal>.csv</> will be appended to the timestamped
2347+
<varname>log_filename</> to create the final log file name.
2348+
(If log_filename ends in <literal>.log</>, the suffix is overwritten.)
2349+
In the case of the example above, the
23502350
file name will be <literal>server_log.1093827753.csv</literal>
23512351
</para>
23522352
</listitem>
@@ -3088,9 +3088,9 @@ SELECT * FROM parent WHERE key = 2400;
30883088
<title>Using the csvlog</title>
30893089

30903090
<para>
3091-
Including <literal>csvlog</> in the <varname>log_destination</> list
3092-
provides a convenient way to import log files into a database table.
3093-
Here is a sample table definition for storing csvlog output:
3091+
Including <literal>csvlog</> in the <varname>log_destination</> list
3092+
provides a convenient way to import log files into a database table.
3093+
Here is a sample table definition for storing csvlog output:
30943094
</para>
30953095

30963096
<programlisting>
@@ -3124,7 +3124,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
31243124

31253125
<para>
31263126
There are a few things you need to import csvlog files easily and
3127-
automatically:
3127+
automatically:
31283128

31293129
<orderedlist>
31303130
<listitem>
@@ -3141,15 +3141,15 @@ guess what
31413141
<listitem>
31423142
<para>
31433143
Set <varname>log_rotation_size</varname> to 0 to disable
3144-
size-based log rotation, as it makes the log filename difficult
3145-
to predict.
3144+
size-based log rotation, as it makes the log filename difficult
3145+
to predict.
31463146
</para>
31473147
</listitem>
31483148

31493149
<listitem>
31503150
<para>
31513151
Set <varname>log_truncate_on_rotate</varname> = on so that old
3152-
log data isn't mixed with the new in the same file.
3152+
log data isn't mixed with the new in the same file.
31533153
</para>
31543154
</listitem>
31553155

@@ -3160,12 +3160,12 @@ guess what
31603160
the same information twice. The COPY command commits all of
31613161
the data it imports at one time, and any single error will
31623162
cause the entire import to fail.
3163-
If you import a partial log file and later import the file again
3164-
when it is complete, the primary key violation will cause the
3165-
import to fail. Wait until the log is complete and closed before
3166-
import. This will also protect against accidently importing a
3167-
partial line that hasn't been completely written, which would
3168-
also cause the COPY to fail.
3163+
If you import a partial log file and later import the file again
3164+
when it is complete, the primary key violation will cause the
3165+
import to fail. Wait until the log is complete and closed before
3166+
import. This will also protect against accidently importing a
3167+
partial line that hasn't been completely written, which would
3168+
also cause the COPY to fail.
31693169
</para>
31703170
</listitem>
31713171
</orderedlist>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp