From 65dc79ac3a46e3ecd84003b3f635ae4740883437 Mon Sep 17 00:00:00 2001 From: Kunal Gupta <39487888+iamKunalGupta@users.noreply.github.com> Date: Fri, 10 Jan 2025 23:42:21 +0530 Subject: [PATCH] Merge pull request #3061 from ClickHouse/feat/add-proxy-warning feat(clickpipes): add warning that pg proxies are not supported for CDC --- .../data-ingestion/clickpipes/postgres/index.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/en/integrations/data-ingestion/clickpipes/postgres/index.md b/docs/en/integrations/data-ingestion/clickpipes/postgres/index.md index 5ea74463371..c24702676c0 100644 --- a/docs/en/integrations/data-ingestion/clickpipes/postgres/index.md +++ b/docs/en/integrations/data-ingestion/clickpipes/postgres/index.md @@ -35,6 +35,12 @@ To get started, you first need to make sure that your Postgres database is set u 7. [Generic Postgres Source](./postgres/source/generic), if you are using any other Postgres provider or using a self-hosted instance +:::warning + +Postgres Proxies like PgBouncer, RDS Proxy, Supabase Pooler, etc., are not supported for CDC based replication. Please make sure to NOT use them for the ClickPipes setup and instead add connection details of the actual Postgres database. + +::: + Once your source Postgres database is set up, you can continue creating your ClickPipe. ## Creating your ClickPipe @@ -67,6 +73,7 @@ Make sure you are logged in to your ClickHouse Cloud account. If you don't have ![Fill in connection details](./images/postgres-connection-details.jpg) +
(Optional) Setting up SSH Tunneling