From b00b6ed3b43a7472ddb37779812a6f963c6c966c Mon Sep 17 00:00:00 2001 From: "devin-ai-integration[bot]" <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Mon, 16 Jun 2025 14:44:26 -0700 Subject: [PATCH] docs: Update Postgres connector docs to reflect CDC replica support in v3.6.21+ (#61644) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: ian.alton@airbyte.io --- docs/integrations/sources/postgres.md | 2 +- docs/integrations/sources/postgres/postgres-troubleshooting.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/integrations/sources/postgres.md b/docs/integrations/sources/postgres.md index 0dfacffab38..2a0ed1ceb25 100644 --- a/docs/integrations/sources/postgres.md +++ b/docs/integrations/sources/postgres.md @@ -100,7 +100,7 @@ These are the additional steps required (after following the [quick start](#quic We recommend following the steps in the [quick start](#quick-start) section to confirm that Airbyte can connect to your Postgres database prior to configuring CDC settings. -For CDC, you must connect to primary/master databases. Pointing the connector configuration to replica database hosts for CDC will lead to failures. +For CDC, you may connect to primary/master databases or replicas. To use a replica as a source, Postgres must be at version 16.1 or later and this connector must be at version 3.6.21 or later. You must also enable additional configurations on the database instance (for help, see the [Postgres official documentation](https://www.postgresql.org/docs/current/warm-standby.html#CASCADING-REPLICATION)). ### Step 2: Provide additional permissions to read-only user diff --git a/docs/integrations/sources/postgres/postgres-troubleshooting.md b/docs/integrations/sources/postgres/postgres-troubleshooting.md index d4bf801dc85..164474e074e 100644 --- a/docs/integrations/sources/postgres/postgres-troubleshooting.md +++ b/docs/integrations/sources/postgres/postgres-troubleshooting.md @@ -36,7 +36,7 @@ There are some notable shortcomings associated with the Xmin replication method: - The modifications you want to capture must be made using `DELETE`/`INSERT`/`UPDATE`. For example, changes made using `TRUNCATE`/`ALTER` will not appear in logs and therefore in your destination. - Schema changes are not supported automatically for CDC sources. Reset and resync data if you make a schema change. - The records produced by `DELETE` statements only contain primary keys. All other data fields are unset. -- Log-based replication only works for master instances of Postgres. CDC cannot be run from a read-replica of your primary database. +- Log-based replication works for master instances of Postgres. CDC can also be run from a read-replica of your primary database starting from Postgres version 16.1 and connector version 3.6.21, provided the replica is [configured to allow this](https://www.postgresql.org/docs/current/warm-standby.html#CASCADING-REPLICATION). - An Airbyte database source using CDC replication can only be used with a single Airbyte destination. This is due to how Postgres CDC is implemented - each destination would receive only part of the data available in the replication slot. - Using logical replication increases disk space used on the database server. The additional data is stored until it is consumed. - Set frequent syncs for CDC to ensure that the data doesn't fill up your disk space.