From 6aa0fdc4aa997adec21b7423e4e08a7ec2bab0ea Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sat, 2 Jul 2005 18:29:04 +0000 Subject: Use on/off consistently for GUC variables in postgresql.conf and the documentation, to match SHOW. --- doc/src/sgml/runtime.sgml | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 42398529866..6b52942786a 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -2461,7 +2461,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows rather than append to, any existing log file of the same name. However, truncation will occur only when a new file is being opened due to time-based rotation, not during server startup or size-based - rotation. When false, pre-existing files will be appended to in + rotation. When off, pre-existing files will be appended to in all cases. For example, using this option in combination with a log_filename like postgresql-%H.log would result in generating twenty-four hourly log files and then @@ -2474,14 +2474,14 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows server_log.Mon, server_log.Tue, etc, and automatically overwrite last week's log with this week's log, set log_filename to server_log.%a, - log_truncate_on_rotation to true, and + log_truncate_on_rotation to on, and log_rotation_age to 1440. Example: To keep 24 hours of logs, one log file per hour, but also rotate sooner if the log file size exceeds 1GB, set log_filename to server_log.%H%M, - log_truncate_on_rotation to true, + log_truncate_on_rotation to on, log_rotation_age to 60, and log_rotation_size to 1000000. Including %M in log_filename allows @@ -3258,7 +3258,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows - This parameter is normally true. When set to false, it disables + This parameter is normally on. When set to off, it disables validation of the function body string during . Disabling validation is @@ -3307,7 +3307,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows A read-only SQL transaction cannot alter non-temporary tables. This parameter controls the default read-only status of each new - transaction. The default is false (read/write). + transaction. The default is off (read/write). @@ -3385,11 +3385,11 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows time zoneAustralian - If set to true, ACST, + If set to on, ACST, CST, EST, and SAT are interpreted as Australian time zones rather than as North/South American time zones and - Saturday. The default is false. + Saturday. The default is off. @@ -3670,12 +3670,12 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' - When true, tables that are referenced by a query + When on, tables that are referenced by a query will be automatically added to the FROM clause if not already present. This behavior does not comply with the SQL standard and many people dislike it because it can mask mistakes (such as referencing a table where you should have - referenced its alias). The default is false. This + referenced its alias). The default is off. This variable can be enabled for compatibility with releases of PostgreSQL prior to 8.1, where this behavior was allowed by default. @@ -3744,7 +3744,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' determines whether OIDs will be included in tables created by SELECT INTO. In PostgreSQL 8.1 default_with_oids is disabled by default; in - prior versions of PostgreSQL, it was true by default. + prior versions of PostgreSQL, it was on by default. @@ -3997,9 +3997,9 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' Reports whether ordinary string literals ('...') treat backslashes literally, as specified in - the SQL standard. The value is currently always false, + the SQL standard. The value is currently always off, indicating that backslashes are treated as escapes. It is planned - that this will change to true in a future + that this will change to on in a future PostgreSQL release when string literal syntax changes to meet the standard. Applications may check this parameter to determine how string literals will be processed. @@ -4164,7 +4164,7 @@ plruby.bar = true # generates error, unknown class name - If true, emit WAL-related debugging output. This option is + If on, emit WAL-related debugging output. This option is only available if the WAL_DEBUG macro was defined when PostgreSQL was compiled. @@ -4181,14 +4181,14 @@ plruby.bar = true # generates error, unknown class name Detection of a damaged page header normally causes PostgreSQL to report an error, aborting the current - command. Setting zero_damaged_pages to true causes + command. Setting zero_damaged_pages to on causes the system to instead report a warning, zero out the damaged page, and continue processing. This behavior will destroy data, namely all the rows on the damaged page. But it allows you to get past the error and retrieve rows from any undamaged pages that may be present in the table. So it is useful for recovering data if corruption has occurred due to hardware or software error. You should - generally not set this true until you have given up hope of recovering + generally not set this on until you have given up hope of recovering data from the damaged page(s) of a table. The default setting is off, and it can only be changed by a superuser. -- cgit v1.2.3