From df858fe58a93be37693b0df9696740477074f2f8 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 26 Jun 2009 22:06:11 +0000 Subject: [PATCH] Marginal improvement of description of recovery_end_command. --- doc/src/sgml/backup.sgml | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index fcf1b8a129..b280859dea 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1,4 +1,4 @@ - + Backup and Restore @@ -1108,8 +1108,9 @@ restore_command = 'cp /mnt/server/archivedir/%f %p' last valid restart point. That is the earliest file that must be kept to allow a restore to be restartable, so this information can be used to truncate the archive to just the minimum required to support - restart of the current restore. %r would only be used in a - warm-standby configuration (see ). + restart from the current restore. %r would typically be + used in a warm-standby configuration + (see ). Write %% to embed an actual % character in the command. @@ -1132,19 +1133,23 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows 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 - recovery_end_command is to provide a mechanism for cleanup following - replication or recovery. + recovery_end_command is to provide a mechanism for cleanup + following replication or recovery. Any %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 can be used to truncate the archive to just the minimum required to - support restart of the current restore. %r would only be - used in a warm-standby configuration (see ). + support restart from the current restore. %r would + typically be used in a warm-standby configuration + (see ). Write %% to embed an actual % character in the command. + + If the command returns a non-zero exit status then a WARNING log - message will be written, unless signalled in which case we return - a FATAL error. + 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.