diff options
| -rw-r--r-- | doc/src/sgml/config.sgml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 4db9831a687..d792b87abf3 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,4 +1,4 @@ -<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.79 2006/09/02 13:12:50 momjian Exp $ --> +<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.80 2006/09/02 21:11:26 momjian Exp $ --> <chapter Id="runtime-config"> <title>Server Configuration</title> @@ -1591,8 +1591,8 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows </indexterm> <listitem> <para> - The <xref linkend="guc-archive-command"> is only invoked on completed - WAL segments. Hence, + By default, the <xref linkend="guc-archive-command"> is only invoked + on completed WAL segments. Hence, if your server generates only little WAL traffic (or has slack periods where it does so), there could be a long delay between the completion of a transaction and its safe recording in archive storage. To put @@ -1602,7 +1602,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows greater than zero, the server will switch to a new segment file whenever this many seconds elapse since the last segment file switch. Note that archived - files that are ended early due to a forced switch are still the same + files that are closed early due to a forced switch are still the same length as completely full files. It is therefore unwise to set a very short <varname>archive_timeout</> — it will bloat your archive storage. <varname>archive_timeout</> settings of a minute or so are |