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 <ian.alton@airbyte.io>

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.