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 ignored unless archive_mode was enabled at server start. If
archive_command is an empty string (the default) while archive_mode is enabled, 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.
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.
- Postgresql WAL archive_command file compare
- use of archive_command in PostgreSQL streaming replication
- PostgreSQL + why archive_command line is marked after baarman restore
- PostgreSQL / WAL-archiving: can I leave archive_command empty when doing image snapshot backups?
- Postgres wal archivation delay
- Re: [HACKERS] Restricting maximum keep segments by repslots
- AW: BUG #15641: Autoprewarm worker fails to start on Windows with huge pages in use Old PostgreSQL community/pgsql-bugs x
- RE: WAL archive (archive_mode = always) ?
- Re: Would it be possible to have parallel archiving?
- Re: Use durable_unlink for .ready and .done files for WAL segment removal