Ship faster with database branching workflows: Add prod-like data to your preview and local dev environments.
Integration guides/Replication

Replicate data to a ClickHouse database on DoubleCloud

Learn how to replicate data from Neon to a ClickHouse database on DoubleCloud

Enrollment Pause for Logical Replication Beta

We have temporarily paused new enrollments in our Logical Replication Beta program. This pause is aimed at evaluating the feature's performance and incorporating feedback from our early adopters. Please stay tuned for updates, and thank you for your interest. We plan to reopen enrollment again soon.


Even when logical replication isn't available on the Neon side, you can schedule DoubleCloud Transfer to copy incremental data from Postgres to ClickHouse at a given interval by enabling periodic snapshots.

Neon's logical replication feature allows you to replicate data from your Neon Postgres database to external destinations.

ClickHouse is an open-source column-oriented database that allows you to query billions of rows in milliseconds. Its architecture is designed to handle analytical queries efficiently, which makes it ideal for data warehousing and analytics applications. Thanks to the columnar storage format, data can be compressed and retrieved more efficiently, allowing some analytical queries to execute 100 times faster compared to traditional databases like Postgres.

DoubleCloud is a managed data platform that helps engineering teams build data infrastructure with zero-maintenance open-source technologies.

In this guide, you will learn how to replicate data from a Neon Postgres database to a managed ClickHouse cluster with DoubleCloud Transfer — a real-time data replication tool. It natively supports ClickHouse data types, data mutations, automated migrations (adding columns), as well as emulating insertions and deletions. With Transfer, you can replicate your data to both managed ClickHouse clusters on DoubleCloud and on-premise ClickHouse instances.


  • A DoubleCloud account

  • A Neon account

  • The ClickHouse client installed on your local machine.


    If you don't have the ClickHouse client, you can install it with the following command:

    curl | sh

    It downloads the official binary for your operating system and installs both the ClickHouse client and ClickHouse itself.

Enable logical replication in Neon


Enabling logical replication modifies the Postgres wal_level configuration parameter, changing it from replica to logical for all databases in your Neon project. Once the wal_level setting is changed to logical, it cannot be reverted. Enabling logical replication also restarts all computes in your Neon project, meaning active connections will be temporarily dropped before automatically reconnecting.

To enable logical replication in Neon:

  1. Select your project in the Neon Console.
  2. On the Neon Dashboard, select Project settings.
  3. Select Beta.
  4. Click Enable to enable logical replication.

You can verify that logical replication is enabled by running the following query from the Neon SQL Editor:

SHOW wal_level;

Create a Postgres role for replication

We recommend using a dedicated Postgres role for replicating data. The role must have the REPLICATION privilege. The default Postgres role created with your Neon project and roles created using the Neon Console, CLI, or API are granted membership in the neon_superuser role, which has the required REPLICATION privilege.

To create a role in the Neon Console:

  1. Navigate to the Neon Console.
  2. Select a project.
  3. Select Roles.
  4. Select the branch where you want to create the role.
  5. Click New Role.
  6. In the role creation dialog, specify a role name.
  7. Click Create.

The role is now created and you are provided with the password for the role, which you can show, copy, or download.

Grant schema access to your Postgres role

If your replication role does not own the schemas and tables you are replicating from, make sure to grant access. Run these commands for each schema:

GRANT USAGE ON SCHEMA <schema_name> TO <role_name>;
GRANT SELECT ON ALL TABLES IN SCHEMA <schema_name> TO <role_name>;

Granting SELECT ON ALL TABLES IN SCHEMA instead of naming the specific tables avoids having to add privileges later if you add tables to your publication.

Unlike replicating to other destinations, you don't need to configure a publication and replication slot manually. DoubleCloud Transfer does that for you automatically.

Add DoubleCloud Transfer's IPs to the allowlist

If you are using Neon's IP Allow feature to limit IP addresses that can connect to Neon, add DoubleCloud Transfer's IPs to your allowlist in Neon:

# IPv6
# IPv4

For instructions, see Configure IP Allow. You'll need to do this before you can validate your connection in the next step. If you are not using Neon's IP Allow feature, you can skip this step.

Create a managed ClickHouse cluster on DoubleCloud


If you already have a ClickHouse instance — for example, an on-premise one — and you want to transfer data there, skip this step and continue with steps described in Create endpoints in DoubleCloud.

  1. Log in to the DoubleCloud console.

  2. In the left menu, select Clusters, click Create cluster, and select ClickHouse.

  3. Select cluster parameters.


    If you're just testing ClickHouse, you can proceed with default parameters that will create a fully functional cluster suitable for testing and development. For production, make sure to select at least three replicas, 16 GB of RAM, and dedicated Keeper hosts to ensure high availability.

  4. Under Basic settings, enter the cluster name, for example clickhouse-dev.

  5. Click Submit at the bottom of the page. Creating a cluster takes around five minutes depending on the provider, region, and settings.

  6. After the cluster status changes from Creating to Alive, select it in the cluster list.

  7. On the Overview tab, find the Connection strings section. Copy the Native interface connection string.

  8. Paste the connection string to ClickHouse client and connect to the cluster.

    The output should look as follows:

    Connected to ClickHouse server version 23.8.9.
    ach-euc1-az2-s1-1.<cluster_name> :)

    :) means that the cluster is ready to receive commands.

  9. Create a database:

  10. Make sure that the database has been created:

     <database_name>  // your database

Create endpoints in DoubleCloud

Before you create a transfer in DoubleCloud, you need to create a source endpoint that fetches data from Neon and a target endpoint that writes the data to ClickHouse.

To create a source endpoint:

  1. In the left menu in the console, select Transfer and navigate to the Endpoints tab.

  2. Click Create endpointSource.

  3. Under Basic settings, select PostgreSQL as the source type.

  4. Enter a name for your source endpoint, for example neon.

  5. Under Endpoint parameters, enter connection details for your Neon database. You can get these details from your Neon connection string, which you'll find in the Connection Details widget on the Dashboard of your Neon project. For example, let's say this is your connection string:


    From this string, the values would show as below. Your actual values will differ, with the exception of the port number.

    • Host:
    • Port: 5432
    • Username: alex
    • Password: AbC123dEf
    • Database Name: dbname
  6. Click Test connection and if it's successful, click Submit.

To create a target endpoint:

  1. In the left menu in the console, select Transfer and navigate to the Endpoints tab.

  2. Click Create endpointTarget.

  3. Under Basic settings, select ClickHouse as the target type.

  4. Enter a name for your source endpoint, for example clickhouse.

  5. If you created a managed ClickHouse cluster in DoubleCloud, select it as the target endpoint in Connection settingsManaged cluster.

    If you want to transfer data to a ClickHouse instance elsewhere, select On-premise in Connection settingsConnection type and specify the connection details.

  6. Enter the database name.

  7. Click Test connection and if it's successful, click Submit.

Create a transfer in DoubleCloud

  1. In the left menu in the console, select Transfer and click Create transfer.

  2. Under Endpoints, select the source and target endpoints you created in the previous step.

  3. Enter the transfer name, for example neon-to-clickhouse.

  4. Under Transfer settings, select Snapshot and replication as the transfer type and specify transfer parameters if needed.


    Even when logical replication isn't available on the Neon side, you can schedule Transfer to copy incremental data from Postgres to ClickHouse at a given interval. For that, enable Periodic snapshot and specify the time period.

  5. Click Submit to create the transfer.

  6. On the transfer page, click Activate.

    When the data has transferred, the transfer status changes to Done.


Need help?

Join our Discord Server to ask questions or see what others are doing with Neon. Users on paid plans can open a support ticket from the console. For more detail, see Getting Support.

Last updated on

Edit this page
Was this page helpful?