How it works...
One good thing about the Installing and configuring repmgr recipe is that it applies to any and all repmgr nodes, except for a few settings that must be distinct on each. These include the node_id, node_name, and conninfo. This makes sense, as each node should have a uniquely identifiable ID and name, and the conninfo parameter should always be set to the local node managed by repmgr.
Once the repmgr.conf configuration file is properly defined, we can clone pgha1 with the repmgr command-line tool. Because no PostgreSQL instance exists on pgha2 yet, this should be a safe operation. Since the new node has no metadata, we must specify the upstream host that we're cloning with -h and the name of the metadata database itself with ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access