1
- <!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.128 2009/06/05 13:40:31 momjian Exp $ -->
1
+ <!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.129 2009/06/26 22:06:11 tgl Exp $ -->
2
2
3
3
<chapter id="backup">
4
4
<title>Backup and Restore</title>
@@ -1108,8 +1108,9 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
1108
1108
last valid restart point. That is the earliest file that must be kept
1109
1109
to allow a restore to be restartable, so this information can be used
1110
1110
to truncate the archive to just the minimum required to support
1111
- restart of the current restore. <literal>%r</> would only be used in a
1112
- warm-standby configuration (see <xref linkend="warm-standby">).
1111
+ restart from the current restore. <literal>%r</> would typically be
1112
+ used in a warm-standby configuration
1113
+ (see <xref linkend="warm-standby">).
1113
1114
Write <literal>%%</> to embed an actual <literal>%</> character
1114
1115
in the command.
1115
1116
</para>
@@ -1132,19 +1133,23 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
1132
1133
<para>
1133
1134
This parameter specifies a shell command that will be executed once only
1134
1135
at the end of recovery. This parameter is optional. The purpose of the
1135
- recovery_end_command is to provide a mechanism for cleanup following
1136
- replication or recovery.
1136
+ <varname> recovery_end_command</> is to provide a mechanism for cleanup
1137
+ following replication or recovery.
1137
1138
Any <literal>%r</> is replaced by the name of the file
1138
1139
containing the last valid restart point. That is the earliest file that
1139
1140
must be kept to allow a restore to be restartable, so this information
1140
1141
can be used to truncate the archive to just the minimum required to
1141
- support restart of the current restore. <literal>%r</> would only be
1142
- used in a warm-standby configuration (see <xref linkend="warm-standby">).
1142
+ support restart from the current restore. <literal>%r</> would
1143
+ typically be used in a warm-standby configuration
1144
+ (see <xref linkend="warm-standby">).
1143
1145
Write <literal>%%</> to embed an actual <literal>%</> character
1144
1146
in the command.
1147
+ </para>
1148
+ <para>
1145
1149
If the command returns a non-zero exit status then a WARNING log
1146
- message will be written, unless signalled in which case we return
1147
- a FATAL error.
1150
+ message will be written and the database will proceed to start up
1151
+ anyway. An exception is that if the command was terminated by a
1152
+ signal, the database will not proceed with startup.
1148
1153
</para>
1149
1154
</listitem>
1150
1155
</varlistentry>
0 commit comments