Enable streaming replication from Azure master to GCP replica. WAL shipping (based on WAL-E) remains as backup.
[This issue is a part of "Migration to GCP. Database-related improvements" database#123 (closed)]
Currently, one of the Postgres replicas on GCP receives data via WAL shipping (organized using WAL-E). The others replicas are following this designated one using streaming replication.
To minimize potential lag for all GCP replicas, it is worth enable streaming replication between primary on Azure and this "1st-layer" dedicated secondary on GCP.
WAL shipping is to be remained as a "backup" option for replication – if HA streaming fails due to some reason, it will enable replica to catch up with master and return to streaming replication mode.
Steps:
-
check Postgres connection between GCP nodes and Azure nodes -
ensure that repmgr will not be affected / will not change or break something once we enable SR -
edit recovery.conf
, the line withprimary_conninfo
to enable SR (no replication slots)
Edited by Nikolay Samokhvalov