Skip to main content
Skip to main content
Edit this page

Azure Flexible Server for Postgres Source Setup Guide

ClickPipes supports Postgres version 12 and later.

Enable Logical Replication​

You don't need to follow the below steps if wal_level is set to logical. This setting should mostly be pre-configured if you are migrating from another data replication tool.

  1. Click on the Server parameters section
Server Parameters in Azure Flexible Server for Postgres
  1. Edit the wal_level to logical
Change wal_level to logical in Azure Flexible Server for Postgres
  1. This change would require a server restart. So restart when requested.
Restart server after changing wal_level

Creating ClickPipes User and Granting permissions​

Connect to your Azure Flexible Server Postgres through the admin user and run the below commands:

  1. Create a Postgres user for exclusively ClickPipes.

  2. Provide read-only access to the schema from which you are replicating tables to the clickpipes_user. Below example shows setting up permissions for the public schema. If you want to grant access to multiple schemas, you can run these three commands for each schema.

  3. Grant replication access to this user:

  4. Create publication that you'll be using for creating the MIRROR (replication) in future.

  5. Set wal_sender_timeout to 0 for clickpipes_user

Add ClickPipes IPs to Firewall​

Please follow the below steps to add ClickPipes IPs to your network.

  1. Go to the Networking tab and add the ClickPipes IPs to the Firewall of your Azure Flexible Server Postgres OR the Jump Server/Bastion if you are using SSH tunneling.
Add ClickPipes IPs to Firewall in Azure Flexible Server for Postgres

What's next?​

You can now create your ClickPipe and start ingesting data from your Postgres instance into ClickHouse Cloud. Make sure to note down the connection details you used while setting up your Postgres instance as you will need them during the ClickPipe creation process.