From 7781916ab5b43d05b83aa2a7a65702dc54e0b796 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 3 Sep 2006 19:06:15 +0000
Subject: [PATCH] Fix non-improvement of description of archive_timeout. 
 archive_command is only invoked on completed WAL segments, period --- there's
 no 'by default' about it.

---
 doc/src/sgml/config.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 52e3d11209..2472c16a3f 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.82 2006/09/02 23:12:16 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.83 2006/09/03 19:06:15 tgl 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>
-        By default, the <xref linkend="guc-archive-command"> is only invoked
-        on completed WAL segments. Hence,
+        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
-- 
2.40.0