PostgreSQL protocol

Connect a stock PostgreSQL client to e6data over the PostgreSQL wire protocol - no e6data driver required.

e6data speaks the PostgreSQL wire protocol, so you can point a stock PostgreSQL client - psql, pgAdmin, DBeaver, Tableau's Postgres connector, or a generic PG-JDBC driver - straight at e6data with nothing to download.

How it works

Connect to the PostgreSQL endpoint (<PG_HOST>:5432) over TLS. The database name encodes the routing as <CLUSTER>/<CATALOG>, your username is your email, and your password is a personal access token. Find your <PG_HOST> and a ready-to-copy connection string in the Console under Cluster → Connectivity.

Connect

psql:

psql "host=<PG_HOST> port=5432 dbname=<CLUSTER>/<CATALOG> user=<EMAIL> sslmode=require"

A full connection URL (password is your PAT):

postgresql://<EMAIL>:e6pat_...@<PG_HOST>:5432/<CLUSTER>/<CATALOG>?sslmode=require&cluster=<CLUSTER>

GUI tools (pgAdmin, DBeaver, Tableau PostgreSQL connector):

Field

Value

Host

<PG_HOST>

Port

5432

Database

<CLUSTER>/<CATALOG>

Username

<EMAIL>

Password

a personal access token

SSL mode

require

BI tools over PostgreSQL

Tableau and pgAdmin connect through their built-in PostgreSQL connectors - no e6data driver needed. Power BI and Looker, which don't have first-class e6data connectors yet, also connect through this PostgreSQL path (they speak to e6data as a Postgres source).

Behavior to know

Suspended cluster: the first connection to a suspended cluster returns SQLSTATE 57P03 ("cluster is being resumed, please retry"). Standard drivers (libpq, psql, recent pgjdbc) retry automatically while the cluster wakes (~30–90 s).
TLS is always required (sslmode=require).
Idle timeout: PostgreSQL sessions have a 1-hour idle timeout by default.

Troubleshooting

Symptom

Likely cause

Fix

Client hangs on a suspended cluster

Driver not honoring 57P03

Update the driver or add app-level retry

Wrong cluster's data

database not in <CLUSTER>/<CATALOG> form

Set the database to <CLUSTER>/<CATALOG>

Connection refused on 5432

PostgreSQL path not enabled, or a firewall block

Confirm the PG endpoint with your admin; open 5432 egress

401-style auth failure

Expired or invalid token

Re-create the token in Profile → Settings