계속 진행하기 전에 Postgres 서비스에 ClickPipes 서비스가 액세스할 수 있는지 확인하십시오. 기본적으로는 가능하지만, IP 액세스를 제한한 경우 ClickHouse 서비스가 위치한 리전에 따라 이 목록에 있는 일부 원본 IP의 액세스를 허용해야 할 수 있습니다.
1
복제 서비스 구성
Fill in the 복제 settings:
- Integration name: A name for this ClickPipe
- ClickHouse 서비스: Select an existing ClickHouse Cloud service or create a new one
- Postgres database: The source database to replicate from
- 복제 method: Choose one of:
- Initial load + CDC: Import existing data and keep tables updated with new changes (recommended)
- Initial load only: One-time snapshot of existing data with no ongoing updates
- CDC only: Skip the initial snapshot and only capture new changes going forward
2
Configure 복제 settings
Fine-tune how data is replicated:
- Sync interval (seconds): How often changes are pulled from Postgres (default: 60)
- Parallel threads for initial load: Number of threads used during the initial snapshot (default: 4)
- Pull batch size: Number of rows fetched per batch during 복제 (default: 100000)
- Snapshot number of rows per partition: Rows per partition during the initial snapshot (default: 100000)
- Snapshot number of tables in parallel: How many tables are snapshotted concurrently (default: 1)
3
Select tables to replicate
Choose a destination database and select which tables to replicate:
- Destination database: Select an existing ClickHouse database or create a new one
- Prefix default destination table names with schema name: Adds the Postgres schema as a prefix to avoid naming conflicts
- Preserve NULL values from source: Maintains NULL values instead of converting to type defaults. 이 설정은 파이프의 모든 테이블에 적용되며, 파이프를 만든 후에는 변경할 수 없습니다.
- Remove deleted rows during merges: For ReplacingMergeTree tables, physically removes deleted rows during background merges
4
Monitor your ClickPipe
Once the ClickPipe starts, you’ll see it listed in the same menu. The initial snapshot of all data may take some time depending on the size of your tables.Click on the integration name to view detailed status, monitor progress, view errors, and manage the ClickPipe. See Lifecycle of a Postgres ClickPipe to understand the different states your ClickPipe may be in.