Type: | string |
Context: | sighup |
Restart: | false |
The local shell command to execute to archive a completed WAL file segment. Any %p
in the string is replaced by the path name of the file to archive, and any %f
is replaced by only the file name. (The path name is relative to the working directory of the server, i.e., the cluster's data directory.) Use %%
to embed an actual %
character in the command. It is important for the command to return a zero exit status only if it succeeds. For more information see backup-archiving-wal.
This parameter can only be set in the postgresql.conf file or on the server command line. It is only used if archive_mode was enabled at server start and archive_library is set to an empty string. If both archive_command
and archive_library are set, an error will be raised. If archive_command
is an empty string (the default) while archive_mode is enabled (and archive_library is set to an empty string), WAL archiving is temporarily disabled, but the server continues to accumulate WAL segment files in the expectation that a command will soon be provided. Setting archive_command
to a command that does nothing but return true, e.g., /bin/true
(REM
on Windows), effectively disables archiving, but also breaks the chain of WAL files needed for archive recovery, so it should only be used in unusual circumstances.
Recommendations
On StackOverflow
On pgsql-hackers
- Force the old transactions logs cleanup even if checkpoint is skipped
- Re: WIP: new system catalog pg_wait_event
- Re: odd buildfarm failure - "pg_ctl: control file appears to be corrupt"
- Re: Requiring recovery.signal or standby.signal when recovering with a backup_label
- Re: pg_rewind WAL segments deletion pitfall