PostgreSQL is an enterprise-grade, open source database management system. Many companies use PostgreSQL as a low-cost data warehousing solution to deliver efficient analytics and user insights.

RudderStack supports PostgreSQL as a source from which you can ingest data and route it to your desired downstream destinations.

Granting permissions

RudderStack requires you to grant certain user permissions on your PostgreSQL warehouse to successfully access data from it.

Run the SQL queries listed in the following sections in the exact order to grant these permissions:

Step 1: Creating the user

• Create a new user RUDDER with a password <strong_unique_password> in PostgreSQL, as shown:

Copy
CREATE USER RUDDER WITH PASSWORD '<strong_unique_password>';

Step 2: Creating the RudderStack schema and granting permissions

1. Create a dedicated schema _rudderstack.

Copy
CREATE SCHEMA "_rudderstack";

2. Grant full access to the schema _rudderstack for the user RUDDER.

Copy
GRANT ALL ON SCHEMA "_rudderstack" TO RUDDER;

3. Grant full access to all the objects in the schema _rudderstack for the user RUDDER.

Copy
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA "_rudderstack" TO RUDDER;

Step 3: Granting permissions on your schema and table

1. To let the user RUDDER look up objects within the schema <YOUR_SCHEMA>, run the command below.

Copy
GRANT USAGE ON SCHEMA "<YOUR_SCHEMA>" TO RUDDER;

2. Grant access to the user RUDDER to read data from the table <YOUR_TABLE>.

Copy
GRANT SELECT ON TABLE "<YOUR_SCHEMA>"."<YOUR_TABLE>" TO RUDDER;

Replace <YOUR_SCHEMA> and <YOUR_TABLE> with the exact names of your PostgreSQL schema and table, respectively.

Optional commands

• To allow the user RUDDER read the data from all the tables in the schema <YOUR_SCHEMA>:

Copy
GRANT SELECT ON ALL TABLES IN SCHEMA "<YOUR_SCHEMA>" TO RUDDER;

• To allow the user RUDDER to read data from all the future tables in the schema <YOUR_SCHEMA>:

Copy
ALTER DEFAULT PRIVILEGES IN SCHEMA "<YOUR_SCHEMA>" GRANT SELECT ON TABLES TO RUDDER;

Replace <YOUR_SCHEMA> with the exact name of your PostgreSQL schema.

Setting up the PostgreSQL source in RudderStack

To set up PostgreSQL as a source in RudderStack, follow these steps:

Naming the source

1. Log into your RudderStack dashboard.
2. From the left navigation bar, go to Source > New Source > Reverse ETL. Then, select PostgreSQL, as shown:

3. Assign a name to your source.

Configuring the connection credentials

1. Choose the relevant option from Table or Model to use the source to sync data from either a warehouse table or a model.

2. Enter the relevant connection details in the Connection Credentials, as shown:

• Host: Enter the host name of your PostgreSQL service.
• Database: Enter the database name in your PostgreSQL instance where the data is loaded.
• User: Specify the username which has the required read/write access to the above database.
• Password: Enter the password for the above user.
• Port: Enter the port number of your PostgreSQL service.
• SSL Mode: Choose the SSL mode through which RudderStack will connect to your PostgreSQL instance. RudderStack provides two options - disable and require. For more information on these options, refer to the FAQ section below.

3. Click Continue. RudderStack will then verify and validate your credentials.

4. Once verified, click Continue to proceed.

Schedule settings

1. Specify the Schedule Settings to schedule the data syncs from your PostgreSQL instance.

2. After specifying the schedule type and run settings, click Continue to finish the setup.

PostgreSQL is now successfully configured as a source in your RudderStack dashboard. You can further connect this source to your preferred destination by clicking on Add Destination button, as shown:

Specifying the data to import

While connecting a destination to your Reverse ETL source, you can use the default JSON mapping or the Visual Data Mapping feature.

FAQ

What are the SSL mode options when setting up the PostgreSQL source in RudderStack?

When setting up a PostgreSQL source, RudderStack provides the following two SSL options:

• disable: SSL mode is disabled when you select this option. Use it in cases where security is not an issue and you don't want any encryption overhead.
• require: When you select this option, your data is encrypted and sent to RudderStack. Use it in cases where security is important and you can deal with the resulting encryption overhead.

What do the three validations under Verifying Credentials imply?

When setting up a Reverse ETL source, once you proceed after entering the connection credentials, you will see the following three validations under the Verifying Credentials option:

These options are explained below:

• Verifying Connection: This option indicates that RudderStack is trying to connect to the warehouse with the information specified in the connection credentials.

• Able to List Schema: This option checks if RudderStack is able to fetch all the schema details using the provided credentials.
• Able to Access RudderStack Schema: This option implies that RudderStack is able to access the _rudderstack schema you have created by successfully running all the commands in the User Permissions section.