Remove example of archive_command from configure section; instead have

users look at the referenced section for examples, per idea from Greg
Smith.

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 0ca5e402e0c42183973ecf4c650322dc403ab603..b65c336cc1f403151b8088e9358efea0f3ea3948 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1,4 +1,4 @@
-
+
 
 
   Server Configuration
@@ -1721,8 +1721,11 @@ SET ENABLE_SEQSCAN TO OFF;
         (The path name is relative to the working directory of the server,
         i.e., the cluster's data directory.)
         Use %% to embed an actual % character in the
-        command. For more information see 
-        linkend="backup-archiving-wal">.
+        command.  It is important for the command to return a zero
+        exit status only if it succeeds. For more information see
+        .
+       
+       
         This parameter can only be set in the postgresql.conf
         file or on the server command line.  It is ignored unless
         archive_mode was enabled at server start.
@@ -1735,14 +1738,6 @@ SET ENABLE_SEQSCAN TO OFF;
         archiving, but also breaks the chain of WAL files needed for
         archive recovery, so it should only be used in unusual circumstances.
        
-       
-        It is important for the command to return a zero exit status if
-        and only if it succeeds.  Examples:
-
-archive_command = 'cp "%p" /mnt/server/archivedir/"%f"'
-archive_command = 'copy "%p" "C:\\server\\archivedir\\%f"'  # Windows
-
-