PostgreSQL

Empower your operations by syncing modeled data from the warehouse back into your database

Unique Identifiers

Hightouch requires a unique identifier in the destination Postgres table in order to add, remove, and update rows. The column must be either a UNIQUE or PRIMARY KEY column. At least one Hightouch field must map to a unique column.

If you're unsure whether your mapping includes a compatible column, just try it! Hightouch will error if you need to change your mappings.

Column Types

Hightouch works out of the box with all standard column types, including:

BIGINT
INT
TEXT
VARCHAR
TIMESTAMPTZ
BOOLEAN
DECIMAL

If you see type errors, it may be because your SQL query is producing the wrong format. Message us on Intercom if you need help!

Required Permissions

Your Postgres credentials must be able to:

Add/update/delete rows from the destination table.
View the INFORMATION_SCHEMA.COLUMNS,

INFORMATION_SCHEMA.TABLE_CONSTRAINTS, and

INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE tables. This is used for

gathering metadata needed for the sync.

Compatible Versions

The minimum supported Postgres version is 9.5 (Hightouch relies on ON CONFLICT for updating rows).

Settings

Your settings for the PostgreSQL destination should look similar to this:

Host: The URL or IP address for your PostgreSQL host. You do not need to include the https://
Port: Your PostgreSQL port. The default- as is typical for PostgreSQL - is 5432.
Database: The name of your database. This is different than the host, but your host address might contain your database name.
Username: The user that has access through Hightouch to the database and tables you want to sync to. You should create a new user specifically for Hightouch access; do not use the root user.
Password: The user's password.

Need help?

Our team is relentlessly focused on your success. We're ready to jump on a call to help unblock you.

Connection issues with your data warehouse?
Confusing API responses from destination systems?
Unsupported destination objects or modes?
Help with complex SQL queries?

Feature Requests?

If you see something that's missing from our app, let us know and we'll work with you to build it!

We want to hear your suggestions for new sources, destinations, and other features that would help you activate your data.