Skip to content

Commit 34b2b1e

Browse files
authored
Merge pull request #4475 from ClickHouse/Blargian-patch-242193
Correct PostgreSQL integration page
2 parents 6c99551 + 51ee9c3 commit 34b2b1e

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

docs/integrations/data-ingestion/dbms/postgresql/connecting-to-postgresql.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,14 @@ import ExperimentalBadge from '@theme/badges/ExperimentalBadge';
1414

1515
This page covers following options for integrating PostgreSQL with ClickHouse:
1616

17-
- using [ClickPipes](/integrations/clickpipes/postgres), the managed integration service for ClickHouse Cloud powered by PeerDB.
18-
- using [PeerDB](https://github.com/PeerDB-io/peerdb), an open-source CDC tool specifically designed for PostgreSQL database replication to both self-hosted ClickHouse and ClickHouse Cloud.
1917
- using the `PostgreSQL` table engine, for reading from a PostgreSQL table
2018
- using the experimental `MaterializedPostgreSQL` database engine, for syncing a database in PostgreSQL with a database in ClickHouse
2119

20+
:::tip
21+
We recommend using [ClickPipes](/integrations/clickpipes/postgres), a managed integration service for ClickHouse Cloud powered by PeerDB.
22+
Alternatively, [PeerDB](https://github.com/PeerDB-io/peerdb) is available as an an open-source CDC tool specifically designed for PostgreSQL database replication to both self-hosted ClickHouse and ClickHouse Cloud.
23+
:::
24+
2225
## Using the PostgreSQL table engine {#using-the-postgresql-table-engine}
2326

2427
The `PostgreSQL` table engine allows **SELECT** and **INSERT** operations on data stored on the remote PostgreSQL server from ClickHouse.

0 commit comments

Comments
 (0)