Google Cloud PostgreSQL

Google Cloud PostgreSQL is a fully-managed database service that helps you set up, maintain, manage, and administer your PostgreSQL relational databases on the Google Cloud platform.

You can ingest data from your Google Cloud PostgreSQL database using Hevo Pipelines and replicate it to a Destination of your choice.

Note: Google Cloud PostgreSQL does not support logical replication. Read the Google Issue for details.

Prerequisites

• IP address or host name of your PostgreSQL server is available.

• The PostgreSQL version is 9.4 or higher.

• Hevo’s IP addresses are whitelisted.

• SELECT, USAGE, and CONNECT privileges are granted to the database user.

---

Perform the following steps to configure your Google Cloud PostgreSQL Source:

Whitelist Hevo’s IP Addresses

You need to whitelist the Hevo IP addresses for your region to enable Hevo to connect to your PostgreSQL database. To do this:

1. Access the Google Cloud console and click on your PostgeSQL instance ID.

   

2. In the left navigation pane, click Connections.

3. Select the Public IP check box to activate access on any custom IP address.

   

4. Click Add Network, and include the list of Hevo IP addresses available for your region.

   

5. Repeat the above step for all the network addresses you want to add.

6. Click Save. You can see Hevo’s IP addresses under Authorized networks.

   

---

Grant Privileges to the User

Grant privileges to the database user connecting to the PostgreSQL database as follows:

1. Log into your PostgreSQL database as a user with grant privilege.

2. Enter the following commands to give accesses to the database user:

    GRANT CONNECT ON DATABASE <database_name> TO <database_username>;
    GRANT USAGE ON SCHEMA <schema_name> TO <database_username>;
    GRANT SELECT ON DATABASE <database_name> TO <database_username>;
   

3. Alter the schema’s default privileges to grant SELECT privileges on tables to the database user:

    ALTER DEFAULT PRIVILEGES IN SCHEMA <schema_name>;
    GRANT SELECT ON TABLES TO <database_username>;
   

---

Limitations

• The data type Array in the Source is automatically mapped to Varchar at the Destination. No other mapping is currently supported.