diff -rcN postgresql/doc/src/sgml/backup.sgml postgresql_with_patch/doc/src/sgml/backup.sgml
*** postgresql/doc/src/sgml/backup.sgml	2011-08-03 05:18:32.000000000 +0900
--- postgresql_with_patch/doc/src/sgml/backup.sgml	2011-08-05 05:48:23.000000000 +0900
***************
*** 724,734 ****
     <title>Making a Base Backup</title>
  
     <para>
!     The procedure for making a base backup is relatively simple:
    <orderedlist>
     <listitem>
      <para>
!      Ensure that WAL archiving is enabled and working.
      </para>
     </listitem>
     <listitem>
--- 724,736 ----
     <title>Making a Base Backup</title>
  
     <para>
!     The procedure for making a base backup is relatively simple. This can
!     also run on the hot standby, the procedure is a little different:
    <orderedlist>
     <listitem>
      <para>
!      Ensure that WAL archiving is enabled and working. This don't need on
!      the hot standby.
      </para>
     </listitem>
     <listitem>
***************
*** 787,793 ****
       This terminates the backup mode and performs an automatic switch to
       the next WAL segment.  The reason for the switch is to arrange for
       the last WAL segment file written during the backup interval to be
!      ready to archive.
      </para>
     </listitem>
     <listitem>
--- 789,811 ----
       This terminates the backup mode and performs an automatic switch to
       the next WAL segment.  The reason for the switch is to arrange for
       the last WAL segment file written during the backup interval to be
!      ready to archive. On the hot standby, this terminates the backup mode
!      only.
!     </para>
!    </listitem>
!    <listitem>
!     <para>
!      Copy <filename>pg_control</> file to the backup taken by above-procedure.
!      This needs on the hot standby.
!     </para>
!    </listitem>
!    <listitem>
!     <para>
!      Check whether the backup is status during hot standby with
!      <application>pg_controldata</application>. This needs on the hot standby.
!      If not (this means that the hot standby promote between
!      <function>pg_stop_backup</> and coping <filename>pg_control</> file),
!      the backup will not recovery.
      </para>
     </listitem>
     <listitem>
***************
*** 807,813 ****
       until the archive succeeds and the backup is complete.
       If you wish to place a time limit on the execution of
       <function>pg_stop_backup</>, set an appropriate
!      <varname>statement_timeout</varname> value.
      </para>
     </listitem>
    </orderedlist>
--- 825,832 ----
       until the archive succeeds and the backup is complete.
       If you wish to place a time limit on the execution of
       <function>pg_stop_backup</>, set an appropriate
!      <varname>statement_timeout</varname> value. On the hot standby, this will
!      act much like not configured <varname>archive_command</> on the primary.
      </para>
     </listitem>
    </orderedlist>