1
1
<!--
2
- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.333 2005/07/01 13 :29:23 momjian Exp $
2
+ $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.334 2005/07/02 18 :29:03 momjian Exp $
3
3
-->
4
4
5
5
<chapter Id="runtime">
@@ -2461,7 +2461,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
2461
2461
rather than append to, any existing log file of the same name.
2462
2462
However, truncation will occur only when a new file is being opened
2463
2463
due to time-based rotation, not during server startup or size-based
2464
- rotation. Whenfalse , pre-existing files will be appended to in
2464
+ rotation. Whenoff , pre-existing files will be appended to in
2465
2465
all cases. For example, using this option in combination with
2466
2466
a <varname>log_filename</varname> like <literal>postgresql-%H.log</literal>
2467
2467
would result in generating twenty-four hourly log files and then
@@ -2474,14 +2474,14 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
2474
2474
<literal>server_log.Mon</literal>, <literal>server_log.Tue</literal>,
2475
2475
etc, and automatically overwrite last week's log with this week's log,
2476
2476
set <varname>log_filename</varname> to <literal>server_log.%a</literal>,
2477
- <varname>log_truncate_on_rotation</varname> to <literal>true </literal>, and
2477
+ <varname>log_truncate_on_rotation</varname> to <literal>on </literal>, and
2478
2478
<varname>log_rotation_age</varname> to <literal>1440</literal>.
2479
2479
</para>
2480
2480
<para>
2481
2481
Example: To keep 24 hours of logs, one log file per hour, but
2482
2482
also rotate sooner if the log file size exceeds 1GB, set
2483
2483
<varname>log_filename</varname> to <literal>server_log.%H%M</literal>,
2484
- <varname>log_truncate_on_rotation</varname> to <literal>true </literal>,
2484
+ <varname>log_truncate_on_rotation</varname> to <literal>on </literal>,
2485
2485
<varname>log_rotation_age</varname> to <literal>60</literal>, and
2486
2486
<varname>log_rotation_size</varname> to <literal>1000000</literal>.
2487
2487
Including <literal>%M</> in <varname>log_filename</varname> allows
@@ -3258,7 +3258,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
3258
3258
</indexterm>
3259
3259
<listitem>
3260
3260
<para>
3261
- This parameter is normallytrue . When set tofalse , it disables
3261
+ This parameter is normallyon . When set tooff , it disables
3262
3262
validation of the function body string during <xref
3263
3263
linkend="sql-createfunction"
3264
3264
endterm="sql-createfunction-title">. Disabling validation is
@@ -3307,7 +3307,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
3307
3307
<para>
3308
3308
A read-only SQL transaction cannot alter non-temporary tables.
3309
3309
This parameter controls the default read-only status of each new
3310
- transaction. The default isfalse (read/write).
3310
+ transaction. The default isoff (read/write).
3311
3311
</para>
3312
3312
3313
3313
<para>
@@ -3385,11 +3385,11 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
3385
3385
<indexterm><primary>time zone</><secondary>Australian</></>
3386
3386
<listitem>
3387
3387
<para>
3388
- If set totrue , <literal>ACST</literal>,
3388
+ If set toon , <literal>ACST</literal>,
3389
3389
<literal>CST</literal>, <literal>EST</literal>, and
3390
3390
<literal>SAT</literal> are interpreted as Australian time
3391
3391
zones rather than as North/South American time zones and
3392
- Saturday. The default isfalse .
3392
+ Saturday. The default isoff .
3393
3393
</para>
3394
3394
</listitem>
3395
3395
</varlistentry>
@@ -3670,12 +3670,12 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
3670
3670
</indexterm>
3671
3671
<listitem>
3672
3672
<para>
3673
- When <literal>true </>, tables that are referenced by a query
3673
+ When <literal>on </>, tables that are referenced by a query
3674
3674
will be automatically added to the <literal>FROM</> clause if
3675
3675
not already present. This behavior does not comply with the
3676
3676
SQL standard and many people dislike it because it can mask
3677
3677
mistakes (such as referencing a table where you should have
3678
- referenced its alias). The default is <literal>false </>. This
3678
+ referenced its alias). The default is <literal>off </>. This
3679
3679
variable can be enabled for compatibility with releases of
3680
3680
<productname>PostgreSQL</> prior to 8.1, where this behavior
3681
3681
was allowed by default.
@@ -3744,7 +3744,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
3744
3744
determines whether OIDs will be included in tables created by
3745
3745
<command>SELECT INTO</command>. In <productname>PostgreSQL</>
3746
3746
8.1 <varname>default_with_oids</> is disabled by default; in
3747
- prior versions of PostgreSQL, it wastrue by default.
3747
+ prior versions of PostgreSQL, it wason by default.
3748
3748
</para>
3749
3749
3750
3750
<para>
@@ -3997,9 +3997,9 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
3997
3997
<para>
3998
3998
Reports whether ordinary string literals
3999
3999
(<literal>'...'</>) treat backslashes literally, as specified in
4000
- the SQL standard. The value is currently always <literal>false </>,
4000
+ the SQL standard. The value is currently always <literal>off </>,
4001
4001
indicating that backslashes are treated as escapes. It is planned
4002
- that this will change to <literal>true </> in a future
4002
+ that this will change to <literal>on </> in a future
4003
4003
<productname>PostgreSQL</productname> release when string literal
4004
4004
syntax changes to meet the standard. Applications may check this
4005
4005
parameter to determine how string literals will be processed.
@@ -4164,7 +4164,7 @@ plruby.bar = true # generates error, unknown class name
4164
4164
</indexterm>
4165
4165
<listitem>
4166
4166
<para>
4167
- Iftrue , emit WAL-related debugging output. This option is
4167
+ Ifon , emit WAL-related debugging output. This option is
4168
4168
only available if the <symbol>WAL_DEBUG</symbol> macro was
4169
4169
defined when <productname>PostgreSQL</productname> was
4170
4170
compiled.
@@ -4181,14 +4181,14 @@ plruby.bar = true # generates error, unknown class name
4181
4181
<para>
4182
4182
Detection of a damaged page header normally causes
4183
4183
<productname>PostgreSQL</> to report an error, aborting the current
4184
- command. Setting <varname>zero_damaged_pages</> totrue causes
4184
+ command. Setting <varname>zero_damaged_pages</> toon causes
4185
4185
the system to instead report a warning, zero out the damaged page,
4186
4186
and continue processing. This behavior <emphasis>will destroy data</>,
4187
4187
namely all the rows on the damaged page. But it allows you to get
4188
4188
past the error and retrieve rows from any undamaged pages that may
4189
4189
be present in the table. So it is useful for recovering data if
4190
4190
corruption has occurred due to hardware or software error. You should
4191
- generally not set thistrue until you have given up hope of recovering
4191
+ generally not set thison until you have given up hope of recovering
4192
4192
data from the damaged page(s) of a table. The
4193
4193
default setting is off, and it can only be changed by a superuser.
4194
4194
</para>