Provide a concrete example of parameter expansion in archive_command.

Per discussion of bug #3877.  Simon Riggs, some fixes by moi.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index a9722c3d38a31fa4e4e64b39caff4401f549cbcc..0031d55c3446cb5dd4ff0aa7d5fee04f203d344a 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -64,7 +64,7 @@ pg_dump <replaceable class="parameter">dbname</replaceable> &gt; <replaceable cl
   </para>
 
   <para>
-   As any other <productname>PostgreSQL</> client application,
+   Like any other <productname>PostgreSQL</> client application,
    <application>pg_dump</> will by default connect with the database
    user name that is equal to the current operating system user name. To override
    this, either specify the <option>-U</option> option or set the
@@ -407,7 +407,7 @@ tar -cf backup.tar /usr/local/pgsql/data
    smaller than an SQL dump. On the contrary, it will most likely be
    larger. (<application>pg_dump</application> does not need to dump
    the contents of indexes for example, just the commands to recreate
-   them.)
+   them.)  However, taking a file system backup might be faster.
   </para>
  </sect1>
 
@@ -556,7 +556,13 @@ archive_command = 'cp -i %p /mnt/server/archivedir/%f &lt;/dev/null'
 </programlisting>
     which will copy archivable WAL segments to the directory
     <filename>/mnt/server/archivedir</>.  (This is an example, not a
-    recommendation, and might not work on all platforms.)
+    recommendation, and might not work on all platforms.)  After the
+    <literal>%p</> and <literal>%f</> parameters have been replaced,
+    the actual command executed might look like this:
+<programlisting>
+cp -i pg_xlog/00000001000000A900000065 /mnt/server/archivedir/00000001000000A900000065 &lt;/dev/null
+</programlisting>
+    A similar command will be generated for each new file to be archived.
    </para>
 
    <para>