*** pgsql/doc/src/sgml/backup.sgml	2009/01/13 00:54:11	2.122
--- pgsql/doc/src/sgml/backup.sgml	2009/03/05 19:50:03	2.123
***************
*** 1,4 ****
! <!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.121 2008/11/09 17:51:15 tgl Exp $ -->
  
  <chapter id="backup">
   <title>Backup and Restore</title>
--- 1,4 ----
! <!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.122 2009/01/13 00:54:11 momjian Exp $ -->
  
  <chapter id="backup">
   <title>Backup and Restore</title>
*************** restore_command = 'copy "C:\\server\\arc
*** 1198,1217 ****
        </listitem>
       </varlistentry>
  
-      <varlistentry id="log-restartpoints"
-                    xreflabel="log_restartpoints">
-       <term><varname>log_restartpoints</varname>
-         (<type>boolean</type>)
-       </term>
-       <listitem>
-        <para>
-         Specifies whether to log each restart point as it occurs. This
-         can be helpful to track the progress of a long recovery.
-         Default is <literal>false</>.
-        </para>
-       </listitem>
-      </varlistentry>
- 
     </variablelist>
  
     </sect3>
--- 1198,1203 ----
*************** if (!triggered)
*** 1865,1871 ****
      backup.  You can do this by running <application>pg_controldata</>
      on the standby server to inspect the control file and determine the
      current checkpoint WAL location, or by using the
!     <varname>log_restartpoints</> option to print values to the server log.
     </para>
    </sect2>
   </sect1>
--- 1851,1857 ----
      backup.  You can do this by running <application>pg_controldata</>
      on the standby server to inspect the control file and determine the
      current checkpoint WAL location, or by using the
!     <varname>log_checkpoints</> option to print values to the server log.
     </para>
    </sect2>
   </sect1>