Man page - barman-switch-wal(1)
Packages contains this manual
- barman-check(1)
- barman-get-wal(1)
- barman-config-update(1)
- barman-verify-backup(1)
- barman-sync-backup(1)
- barman-show-backup(1)
- barman-restore(1)
- barman-switch-wal(1)
- barman-verify(1)
- barman-put-wal(1)
- barman-check-backup(1)
- barman-sync-info(1)
- barman-rebuild-xlogdb(1)
- barman-switch-xlog(1)
- barman-diagnose(1)
- barman-replication-status(1)
- barman-keep(1)
- barman-wal-archive(1)
- barman-cron(1)
- barman-wal-restore(1)
- barman-delete(1)
- barman-terminate-process(1)
- barman-list-files(1)
- barman-archive-wal(1)
- barman-show-servers(1)
- barman-status(1)
- barman-generate-manifest(1)
- barman-list-processes(1)
- barman-backup(1)
- barman-config-switch(1)
- barman-list-servers(1)
- barman-receive-wal(1)
- barman-sync-wals(1)
- barman-lock-directory-cleanup(1)
- barman-list_backups(1)
apt-get install barman-cli
Manual
BARMAN-SWITCH-WAL
NAMESYNOPSIS
DESCRIPTION
PARAMETERS
AUTHOR
COPYRIGHT
NAME
barman-switch-wal - Barman Sub-Commands
SYNOPSIS
switch-wal
[ --archive ]
[ --archive-timeout ]
[ --force ]
[ { -h | --help } ]
SERVER_NAME [ SERVER_NAME ... ]
DESCRIPTION
Execute pg_switch_wal() on the target server (Postgres versions 10 and later) or pg_switch_xlog() (for Postgres versions 8.3 to 9.6).
PARAMETERS
SERVER_NAME
Name of the server in barman node
--archive
Waits for one WAL file to be archived. If no WAL file is archived within a specified time (default: 30 seconds), Barman will terminate with a failure exit code. This option is also available on standby servers.
--archive-timeout
Specify the amount of time in seconds (default: 30 seconds) that the archiver will wait for a new WAL file to be archived before timing out. This option is also available on standby servers.
--force
Forces the switch by executing a CHECKPOINT before pg_switch_wal() .
NOTE:
Running a CHECKPOINT may increase I/O load on the Postgres server, so use this option cautiously.
-h / --help
Show a help message and exit. Provides information about command usage.
AUTHOR
EnterpriseDB
COPYRIGHT
© Copyright EnterpriseDB UK Limited 2011-2025