[docs] Note about replication in managed cloud providers

I've added a note saying that some managed offerings actually replicate the replication slot.

I found this information very critical when evaluating reliability of Debezium. I'll look for links in the docs tomorrow. [Patroni](https://patroni.readthedocs.io/en/latest/) also seems to support this feature.
This commit is contained in:
Jannik Steinmann 2022-08-31 17:25:41 +02:00 committed by Jiri Pechanec
parent 196d24f2be
commit 9f811a6f64
2 changed files with 6 additions and 0 deletions

View File

@ -153,6 +153,7 @@ Grzegorz Kołakowski
Jacob Gminder Jacob Gminder
Jan Doms Jan Doms
Jan Hendrik Dolling Jan Hendrik Dolling
Jannik Steinmann
Jason Schweier Jason Schweier
Jiabao Sun Jiabao Sun
Juan Fiallo Juan Fiallo

View File

@ -3280,6 +3280,11 @@ As of release 12, PostgreSQL allows logical replication slots _only on primary s
Also, replication slots themselves are not propagated to replicas. Also, replication slots themselves are not propagated to replicas.
If the primary server goes down, a new primary must be promoted. If the primary server goes down, a new primary must be promoted.
[NOTE]
====
Some managed PostgresSQL services (AWS RDS and GCP CloudSQL for example) implement replication to a standby via disk replication. This means that the replication slot does get replicated and will remain available after a failover.
====
ifdef::community[] ifdef::community[]
The new primary must have the xref:{link-postgresql-connector}#installing-postgresql-output-plugin[logical decoding plug-in] installed and a replication slot that is configured for use by the plug-in and the database for which you want to capture changes. Only then can you point the connector to the new server and restart the connector. The new primary must have the xref:{link-postgresql-connector}#installing-postgresql-output-plugin[logical decoding plug-in] installed and a replication slot that is configured for use by the plug-in and the database for which you want to capture changes. Only then can you point the connector to the new server and restart the connector.
endif::community[] endif::community[]