11<!--
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 $
33-->
44
55<chapter Id="runtime">
@@ -2461,7 +2461,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
24612461 rather than append to, any existing log file of the same name.
24622462 However, truncation will occur only when a new file is being opened
24632463 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
24652465 all cases. For example, using this option in combination with
24662466 a <varname>log_filename</varname> like <literal>postgresql-%H.log</literal>
24672467 would result in generating twenty-four hourly log files and then
@@ -2474,14 +2474,14 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
24742474 <literal>server_log.Mon</literal>, <literal>server_log.Tue</literal>,
24752475 etc, and automatically overwrite last week's log with this week's log,
24762476 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
24782478 <varname>log_rotation_age</varname> to <literal>1440</literal>.
24792479 </para>
24802480 <para>
24812481 Example: To keep 24 hours of logs, one log file per hour, but
24822482 also rotate sooner if the log file size exceeds 1GB, set
24832483 <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>,
24852485 <varname>log_rotation_age</varname> to <literal>60</literal>, and
24862486 <varname>log_rotation_size</varname> to <literal>1000000</literal>.
24872487 Including <literal>%M</> in <varname>log_filename</varname> allows
@@ -3258,7 +3258,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
32583258 </indexterm>
32593259 <listitem>
32603260 <para>
3261- This parameter is normallytrue . When set tofalse , it disables
3261+ This parameter is normallyon . When set tooff , it disables
32623262 validation of the function body string during <xref
32633263 linkend="sql-createfunction"
32643264 endterm="sql-createfunction-title">. Disabling validation is
@@ -3307,7 +3307,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
33073307 <para>
33083308 A read-only SQL transaction cannot alter non-temporary tables.
33093309 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).
33113311 </para>
33123312
33133313 <para>
@@ -3385,11 +3385,11 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
33853385 <indexterm><primary>time zone</><secondary>Australian</></>
33863386 <listitem>
33873387 <para>
3388- If set totrue , <literal>ACST</literal>,
3388+ If set toon , <literal>ACST</literal>,
33893389 <literal>CST</literal>, <literal>EST</literal>, and
33903390 <literal>SAT</literal> are interpreted as Australian time
33913391 zones rather than as North/South American time zones and
3392- Saturday. The default isfalse .
3392+ Saturday. The default isoff .
33933393 </para>
33943394 </listitem>
33953395 </varlistentry>
@@ -3670,12 +3670,12 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
36703670 </indexterm>
36713671 <listitem>
36723672 <para>
3673- When <literal>true </>, tables that are referenced by a query
3673+ When <literal>on </>, tables that are referenced by a query
36743674 will be automatically added to the <literal>FROM</> clause if
36753675 not already present. This behavior does not comply with the
36763676 SQL standard and many people dislike it because it can mask
36773677 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
36793679 variable can be enabled for compatibility with releases of
36803680 <productname>PostgreSQL</> prior to 8.1, where this behavior
36813681 was allowed by default.
@@ -3744,7 +3744,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
37443744 determines whether OIDs will be included in tables created by
37453745 <command>SELECT INTO</command>. In <productname>PostgreSQL</>
37463746 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.
37483748 </para>
37493749
37503750 <para>
@@ -3997,9 +3997,9 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
39973997 <para>
39983998 Reports whether ordinary string literals
39993999 (<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 </>,
40014001 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
40034003 <productname>PostgreSQL</productname> release when string literal
40044004 syntax changes to meet the standard. Applications may check this
40054005 parameter to determine how string literals will be processed.
@@ -4164,7 +4164,7 @@ plruby.bar = true # generates error, unknown class name
41644164 </indexterm>
41654165 <listitem>
41664166 <para>
4167- Iftrue , emit WAL-related debugging output. This option is
4167+ Ifon , emit WAL-related debugging output. This option is
41684168 only available if the <symbol>WAL_DEBUG</symbol> macro was
41694169 defined when <productname>PostgreSQL</productname> was
41704170 compiled.
@@ -4181,14 +4181,14 @@ plruby.bar = true # generates error, unknown class name
41814181 <para>
41824182 Detection of a damaged page header normally causes
41834183 <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
41854185 the system to instead report a warning, zero out the damaged page,
41864186 and continue processing. This behavior <emphasis>will destroy data</>,
41874187 namely all the rows on the damaged page. But it allows you to get
41884188 past the error and retrieve rows from any undamaged pages that may
41894189 be present in the table. So it is useful for recovering data if
41904190 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
41924192 data from the damaged page(s) of a table. The
41934193 default setting is off, and it can only be changed by a superuser.
41944194 </para>