> ## Documentation Index
> Fetch the complete documentation index at: https://private-7c7dfe99-mintlify-8a08bda2.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
> Set up Neon Postgres instance as a source for ClickPipes
# Neon Postgres source setup guide
export const Image = ({img, alt, size}) => {
return
;
};
This is a guide on how to setup Neon Postgres, which you can use for replication in ClickPipes.
Make sure you're signed in to your [Neon console](https://console.neon.tech/app/projects) for this setup.
Creating a user with permissions
Connect to your Neon instance as an admin user and execute the following commands:
1. Create a dedicated user for ClickPipes:
```sql theme={null}
CREATE USER clickpipes_user PASSWORD 'some-password';
```
2. Grant schema-level, read-only access to the user you created in the previous step. The following example shows permissions for the `public` schema. Repeat these commands for each schema containing tables you want to replicate:
```sql theme={null}
GRANT USAGE ON SCHEMA "public" TO clickpipes_user;
GRANT SELECT ON ALL TABLES IN SCHEMA "public" TO clickpipes_user;
ALTER DEFAULT PRIVILEGES IN SCHEMA "public" GRANT SELECT ON TABLES TO clickpipes_user;
```
3. Grant replication privileges to the user:
```sql theme={null}
ALTER USER clickpipes_user WITH REPLICATION;
```
4. Create a [publication](https://www.postgresql.org/docs/current/logical-replication-publication.html) with the tables you want to replicate. We strongly recommend only including the tables you need in the publication to avoid performance overhead.
Any table included in the publication must either have a **primary key** defined *or* have its **replica identity** configured to `FULL`. See the [Postgres FAQs](/integrations/clickpipes/postgres/faq#how-should-i-scope-my-publications-when-setting-up-replication) for guidance on scoping.
* To create a publication for specific tables:
```sql theme={null}
CREATE PUBLICATION clickpipes FOR TABLE table_to_replicate, table_to_replicate2;
```
* To create a publication for all tables in a specific schema:
```sql theme={null}
CREATE PUBLICATION clickpipes FOR TABLES IN SCHEMA "public";
```
The `clickpipes` publication will contain the set of change events generated from the specified tables, and will later be used to ingest the replication stream.
Enable logical replication
In Neon, you can enable logical replication through the UI. This is necessary for ClickPipes's CDC to replicate data.
Head over to the **Settings** tab and then to the **Logical Replication** section.
Click on **Enable** to be all set here. You should see the below success message once you enable it.
Let's verify the below settings in your Neon Postgres instance:
```sql theme={null}
SHOW wal_level; -- should be logical
SHOW max_wal_senders; -- should be 10
SHOW max_replication_slots; -- should be 10
```
IP whitelisting (for Neon enterprise plan)
If you have Neon Enterprise plan, you can whitelist the [ClickPipes IPs](/integrations/clickpipes/home#list-of-static-ips) to allow replication from ClickPipes to your Neon Postgres instance.
To do this you can click on the **Settings** tab and go to the **IP Allow** section.
Copy connection details
Now that we have the user, publication ready and replication enabled, we can copy the connection details to create a new ClickPipe.
Head over to the **Dashboard** and at the text box where it shows the connection string,
change the view to **Parameters Only**. We will need these parameters for our next step.
What's next?
You can now [create your ClickPipe](/integrations/clickpipes/postgres) 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.