On Wed, 2006-09-06 at 12:01 -0400, Bruce Momjian wrote:
> Simon Riggs wrote:
> > 
> > Likely to be completed by end of next week now, submitted in chunks:
> > 
> > 1. Notes on restartable recovery

Included here

> > 2. Notes on standby functionality
> > 3. discussion on rolling your own record-level polling using
> > pg_xlogfile_name_offset()
> 
> > 4. pg_standby.c sample code
> 
> I need #4 long before the end of _this_ week, or it is going to be
> rejected for 8.2.  The documentation can be added even during beta,
> though the earlier the better so it can be tested.

I guess I was thinking to put #4 in the docs rather than contrib... but
I won't be able to make this deadline either way now.

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com
Index: doc/src/sgml/backup.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/backup.sgml,v
retrieving revision 2.83
diff -c -r2.83 backup.sgml
*** doc/src/sgml/backup.sgml	17 Aug 2006 23:04:02 -0000	2.83
--- doc/src/sgml/backup.sgml	8 Sep 2006 17:47:46 -0000
***************
*** 855,861 ****
     <listitem>
      <para>
       Start the server.  The server will go into recovery mode and
!      proceed to read through the archived WAL files it needs.  Upon completion
       of the recovery process, the server will rename
       <filename>recovery.conf</> to <filename>recovery.done</> (to prevent
       accidentally re-entering recovery mode in case of a crash later) and then
--- 855,863 ----
     <listitem>
      <para>
       Start the server.  The server will go into recovery mode and
!      proceed to read through the archived WAL files it needs.  Should the
!      recovery be terminated because of an external error, the server can
!      simply be restarted and it will continue recovery.  Upon completion
       of the recovery process, the server will rename
       <filename>recovery.conf</> to <filename>recovery.done</> (to prevent
       accidentally re-entering recovery mode in case of a crash later) and then
***************
*** 935,941 ****
        recover to such a time, you must go back to your previous base backup
        and roll forward from there.)
       </para>
!     </note>
  
      <sect3 id="recovery-config-settings" xreflabel="Recovery Settings">
       <title>Recovery Settings</title>
--- 937,957 ----
        recover to such a time, you must go back to your previous base backup
        and roll forward from there.)
       </para>
!    </note>
! 
!    <para>
!     If recovery finds a corruption in the WAL data then recovery will
!     complete at that point and the server will not start. The recovery 
!     process could be re-run from the beginning, specifying a 
!     <quote>recovery target</> so that recovery can complete normally.
!     If recovery fails for an external reason, such as a system crash or
!     the WAL archive has become inaccessible, then the recovery can be
!     simply restarted and it will restart almost from where it failed.
!     Restartable recovery works by writing a restartpoint record to the control
!     file at the first safely usable checkpoint record found after 
!     <varname>checkpoint_timeout</> seconds. 
!    </para>
! 
  
      <sect3 id="recovery-config-settings" xreflabel="Recovery Settings">
       <title>Recovery Settings</title>
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Reply via email to