System Exception: GCP Secondary Postgres is relying on S3 Archiving instead of Streaming Replication
As part of #151 (closed), for various reasons, we have thus far been unable to setup and maintain a Azure-GCP Postgres streaming secondary.
As a workaround in https://docs.google.com/document/d/1BkBbGNb0SK8oGjWPZCqiV4verek88JG25ATgu9XaUKw/edit, the decision was made to use Postgres S3 Archive replication to the secondary only.
The plan is to switch over from archiving to streaming in future, once the git transfer has started.
The root cause of the problem with streaming replication needs to be resolved before the GCP Switchover.
This issue is to track this exception in the Infrastructure Agenda doc
cc @stanhu @jarv @ilyaf @ahanselka @_stark