1- <!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.79 2006/09/0213:12:50 momjian Exp $ -->
1+ <!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.80 2006/09/0221:11:26 momjian Exp $ -->
22
33<chapter Id="runtime-config">
44 <title>Server Configuration</title>
@@ -1591,8 +1591,8 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
15911591 </indexterm>
15921592 <listitem>
15931593 <para>
1594- The <xref linkend="guc-archive-command"> is only invoked on completed
1595- WAL segments. Hence,
1594+ By default, the <xref linkend="guc-archive-command"> is only invoked
1595+ on completed WAL segments. Hence,
15961596 if your server generates only little WAL traffic (or has slack periods
15971597 where it does so), there could be a long delay between the completion
15981598 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
16021602 greater than zero, the server will switch to a new segment file
16031603 whenever this many seconds elapse since the last segment file switch.
16041604 Note that archived
1605- files that areended early due to a forced switch are still the same
1605+ files that areclosed early due to a forced switch are still the same
16061606 length as completely full files. It is therefore unwise to set a very
16071607 short <varname>archive_timeout</> — it will bloat your archive
16081608 storage. <varname>archive_timeout</> settings of a minute or so are