> ## Documentation Index
> Fetch the complete documentation index at: https://private-7c7dfe99-mintlify-3a82795f.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
> Set up Google Cloud SQL Postgres instance as a source for ClickPipes
# Google Cloud SQL Postgres source setup guide
export const Image = ({img, alt, size}) => {
return
;
};
If you use one of the supported providers (in the sidebar), please refer to the specific guide for that provider.
Supported Postgres versions
Anything on or after Postgres 12
Enable logical replication
**You don't need** to follow the below steps if the setting `cloudsql. logical_decoding` is on. This setting should mostly be pre-configured if you're migrating from another data replication tool.
1. Click on **Edit** button on the Overview page.
2. Go to Flags and change `cloudsql.logical_decoding` to on. This change will need restarting your Postgres server.
Creating ClickPipes user and granting permissions
Connect to your Cloud SQL Postgres through the admin user and run the below 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.
[//]: # "TODO Add SSH Tunneling"
Add ClickPipes IPs to Firewall
Please follow the below steps to add ClickPipes IPs to your network.
If your are using SSH Tunneling, then you need to add the [ClickPipes IPs](/integrations/clickpipes/home#list-of-static-ips) to the firewall rules of the Jump Server/Bastion.
1. Go to **Connections** section
2. Go to the Networking subsection
3. Add the [public IPs of ClickPipes](/integrations/clickpipes/home#list-of-static-ips)
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.