repmgr standby follow repmgr standby follow repmgr standby follow attach a running standby to a new upstream node Attaches the standby to a new upstream node. This command requires a valid repmgr.conf file for the standby, either specified explicitly with -f/--config-file or located in a default location; no additional arguments are required. To re-add an inactive node to the replication cluster, use . This command will force a restart of the standby server, which must be running. Additionally, in order to be able to verify whether the standby can attach to the upstream node, a CHECKPOINT will be executed - this requires superuser privileges, and will be executed even with the --dry-run option. If the &repmgr; database user is not a superuser, it will not be possible to execute CHECKPOINT, meaning &repmgr; may not be able to determine whether the upstream node can be followed. repmgr standby follow will wait up to standby_follow_timeout seconds (default: 30) to verify the standby has actually connected to the new primary. $ repmgr -f /etc/repmgr.conf standby follow INFO: setting node 3's primary to node 2 NOTICE: restarting server using "pg_ctl -l /var/log/postgres/startup.log -w -D '/var/lib/postgres/data' restart" waiting for server to shut down........ done server stopped waiting for server to start.... done server started NOTICE: STANDBY FOLLOW successful DETAIL: node 3 is now attached to node 2 --dry-run Check prerequisites but don't actually follow a new standby. This does not guarantee the standby can follow the primary; in particular, whether the primary and standby timelines have diverged, can currently only be determined by actually attempting to attach the standby to the primary. --upstream-node-id Node ID of the new primary. This option is intended for use by repmgrd, when instructing standbys to follow the new primary. For more details see Automatic failover configuration. -w --wait Wait for a primary to appear. &repmgr; will wait for up to primary_follow_timeout seconds (default: 60 seconds) to verify that the standby is following the new primary. This value can be defined in repmgr.conf. Following exit codes can be emitted by repmgr standby follow: SUCCESS (0) No issues were detected. ERR_DB_CONN (6) &repmgr; was unable to establish a database connection to one of the nodes. ERR_FOLLOW_FAIL (23) &repmgr; was unable to complete the follow command. A standby_follow event notification will be generated. If provided, &repmgr; will substitute the placeholders %p with the node ID of the primary being followed, %c with its conninfo string, and %a with its node name.