Changeset 133

Show
Ignore:
Timestamp:
04/22/10 20:02:29 (9 years ago)
Author:
depesz
Message:

Blocking the delay during initial recovery is not possible - we can't reliably check whether we are during it :(

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • trunk/omnipitr/doc/omnipitr-restore.pod

    r132 r133  
    2626This is primarily used to keep window of safety before I<DELETE * FROM 
    2727main_table> will be applied on slave database. 
    28  
    29 This delay does not apply to initial recovery (getting system from backup till 
    30 "Minimum recovery ending location"). Reason for this is simple - before reaching 
    31 minimum recovery ending location database can be in nonconsistent state. So 
    32 there is no point in stalling till we get to point where database is consistent. 
    3328 
    3429=item --finish-trigger (-f)