repmgr standby switchover repmgr standby switchover repmgr standby switchover promote a standby to primary and demote the existing primary to a standby Promotes a standby to primary and demotes the existing primary to a standby. This command must be run on the standby to be promoted, and requires a passwordless SSH connection to the current primary. If other standbys are connected to the demotion candidate, &repmgr; can instruct these to follow the new primary if the option --siblings-follow is specified. --always-promote Promote standby to primary, even if it is behind original primary (original primary will be shut down in any case). --dry-run Check prerequisites but don't actually execute a switchover. -F --force Ignore warnings and continue anyway. --force-rewind Use pg_rewind to reintegrate the old primary if necessary (PostgreSQL 9.5 and later). -R --remote-user System username for remote SSH operations (defaults to local system user). --siblings-follow Have standbys attached to the old primary follow the new primary. Execute with the --dry-run option to test the switchover as far as possible without actually changing the status of either node. repmgrd should not be active on any nodes while a switchover is being executed. This restriction may be lifted in a later version. standby_switchover and standby_promote event notifications will be generated for the new primary, and a node_rejoin event notification for the former primary (new standby). If using an event notification script, standby_switchover will populate the placeholder parameter %p with the node ID of the former standby. For more details see the section .