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.

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 52e3d11209cd102162af6923d6fbdb83539aebd4..2472c16a3f61cb02804909febd2b214fd1860e01 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1,4 +1,4 @@
-
+
 
 
   Server Configuration
@@ -1591,8 +1591,8 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"'  # Windows
       
       
        
-        By default, the  is only invoked
-        on completed WAL segments. Hence,
+        The  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