My test environment had network glitch over the weekend and I ended up having two Primary databases up and running in the cluster.
ID | Name | Role | Status | Upstream | Location | Priority | Connection string
----+-----------------------------------+---------+-----------+----------+----------+----------+------------------------------------------------------------------------------------
1 | node-1 | primary | ! running | | default | 100 | host=node-1 user=repmgr dbname=repmgr connect_timeout=2
2 | node-2 | primary | * running | | default | 100 | host=node-2 user=repmgr dbname=repmgr connect_timeout=2
Is there a way to demote the new Primary back to Standby and resume WAL shipping instead of perform the Standby clone?
Postgres version: 10.7
Repmgr version: 4.3