repmgr standby follow

repmgr standby follow

attach a standby to a new primary

## Description

Attaches the standby to a new primary. 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.

This command will force a restart of the standby server, which must be running. It can only be used to attach an active standby to the current primary node (and not to another standby).

To re-add an inactive node to the replication cluster, use repmgr-node-rejoin.

`repmgr standby follow` will wait up to `standby_follow_timeout` seconds (default: `30`) to verify the standby has actually connected to the new primary.

## Example

          $ 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

## Options

`--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.

`-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`.

## Event notifications

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.

## See also

repmgr-node-rejoin