*** pgsql/doc/src/sgml/recovery-config.sgml	2010/02/25 09:32:19	2.2
--- pgsql/doc/src/sgml/recovery-config.sgml	2010/03/18 09:17:18	2.3
***************
*** 1,4 ****
! <!-- $PostgreSQL: pgsql/doc/src/sgml/recovery-config.sgml,v 2.1 2010/02/22 11:47:30 heikki Exp $ -->
  
  <chapter Id="recovery-config">
    <title>Recovery Configuration</title>
--- 1,4 ----
! <!-- $PostgreSQL: pgsql/doc/src/sgml/recovery-config.sgml,v 2.2 2010/02/25 09:32:19 heikki Exp $ -->
  
  <chapter Id="recovery-config">
    <title>Recovery Configuration</title>
*************** restore_command = 'copy "C:\\server\\arc
*** 59,72 ****
        </listitem>
       </varlistentry>
  
!      <varlistentry id="recovery-end-command" xreflabel="recovery_end_command">
!       <term><varname>recovery_end_command</varname> (<type>string</type>)</term>
        <listitem>
         <para>
!         This parameter specifies a shell command that will be executed once only
!         at the end of recovery. This parameter is optional. The purpose of the
!         <varname>recovery_end_command</> is to provide a mechanism for cleanup
!         following replication or recovery.
          Any <literal>%r</> is replaced by the name of the file
          containing the last valid restart point. That is the earliest file that
          must be kept to allow a restore to be restartable, so this information
--- 59,73 ----
        </listitem>
       </varlistentry>
  
!      <varlistentry id="restartpoint-command" xreflabel="restartpoint_command">
!       <term><varname>restartpoint_command</varname> (<type>string</type>)</term>
        <listitem>
         <para>
!         This parameter specifies a shell command that will be executed at
!         every restartpoint. This parameter is optional. The purpose of the
!         <varname>restartpoint_command</> is to provide a mechanism for cleaning
!         up old archived WAL files that are no longer needed by the standby
!         server.
          Any <literal>%r</> is replaced by the name of the file
          containing the last valid restart point. That is the earliest file that
          must be kept to allow a restore to be restartable, so this information
*************** restore_command = 'copy "C:\\server\\arc
*** 79,84 ****
--- 80,103 ----
         </para>
         <para>
          If the command returns a non-zero exit status then a WARNING log
+         message will be written.
+        </para>
+       </listitem>
+      </varlistentry>
+ 
+      <varlistentry id="recovery-end-command" xreflabel="recovery_end_command">
+       <term><varname>recovery_end_command</varname> (<type>string</type>)</term>
+       <listitem>
+        <para>
+         This parameter specifies a shell command that will be executed once only
+         at the end of recovery. This parameter is optional. The purpose of the
+         <varname>recovery_end_command</> is to provide a mechanism for cleanup
+         following replication or recovery.
+         Any <literal>%r</> is replaced by the name of the file containing the
+         last valid restart point, like in <xref linkend="restartpoint-command">.
+        </para>
+        <para>
+         If the command returns a non-zero exit status then a WARNING log
          message will be written and the database will proceed to start up
          anyway.  An exception is that if the command was terminated by a
          signal, the database will not proceed with startup.