The local shell command to execute to retrieve an archived segment of the WAL file series. This parameter is required for archive recovery, but optional for streaming replication. Any
%f in the string is replaced by the name of the file to retrieve from the archive, and any
%p is replaced by the copy destination path name on the server. (The path name is relative to the current working directory, i.e., the cluster's data directory.) 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 restarting from the current restore.
%r is typically only used by warm-standby configurations (see warm-standby). Write
%% to embed an actual
It is important for the command to return a zero exit status only if it succeeds. The command will be asked for file names that are not present in the archive; it must return nonzero when so asked. Examples:restore_command = 'cp /mnt/server/archivedir/%f "%p"'restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows An exception is that if the command was terminated by a signal (other than SIGTERM, which is used as part of a database server shutdown) or an error by the shell (such as command not found), then recovery will abort and the server will not start up.
This parameter can only be set at server start.
- PostgreSQL 9.1 streaming replication restore_command: special meaning of exit code 255?
- Is it mandatory to set "restore_command" and "archive_cleanup_command" in recovery.conf?
- Hot standby is falling behind -- how to speed up WAL ingestion rate from `restore_command` in PostgreSQL?
- use of archive_command in PostgreSQL streaming replication
- wal_keep_segments why minimum, not maximum?
- Re: allow online change primary_conninfo
- recovery starting when backup_label exists, but not recovery.signal
- pg_rewind is failing on PG v12 BETA/PG HEAD
- Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line
- Re: recovery starting when backup_label exists, but not recovery.signal