Postgres

Summation connects to PostgreSQL and any compatible flavor (Amazon RDS, Aurora Postgres, Cloud SQL, Azure Database for PostgreSQL, Supabase, Neon, etc.) using standard host/port credentials.

What you’ll need

A reachable host and port (default 5432).
A database name.
A user with CONNECT on the database, USAGE on the schemas, and SELECT on the tables you want exposed. See GRANT in the Postgres docs.
For most managed providers, an SSL mode that matches the server’s TLS configuration. See SSL Support.

Create a dedicated read-only role for Summation. Its queries are then auditable and there’s no way for the connector to modify data.

Where to find host/port for your provider

Provider	Where to look
Amazon RDS / Aurora	RDS console → your DB instance → Connectivity & security → Endpoint and port. See Connecting to a DB instance.
Google Cloud SQL	Cloud SQL console → your instance → Connections. See About connection options.
Azure Database for PostgreSQL	Azure portal → your server → Overview. See Connect with Azure CLI.
Supabase	Project dashboard → Project Settings → Database → Connection info. See Connect to Postgres.
Neon	Project dashboard → Connection Details. See Connect to your database.

Form fields

Field	Required	Stored as	API key	Notes
Host	Yes	Config	`pg_host`	DNS name or IP, e.g. `db.example.com`.
Port	Yes	Config	`pg_port`	Default `5432`.
Database	Yes	Config	`pg_db`	The Postgres database name (not a schema).
Username	Yes	Config	`pg_user`	Login role.
Password	Yes	Secret	`pg_pass`
SSL Mode	Optional	Config	`pg_sslmode`	One of `disable`, `prefer`, `require`, `verify-ca`, `verify-full`. Default `prefer`. See SSL Mode descriptions.
CA Certificate	Optional	Secret	`pg_sslrootcert`	Upload or paste a PEM CA bundle for `verify-ca` / `verify-full`. Required when SSL Mode is `verify-ca` or `verify-full`. See SSL Client File Usage.
Connection Pool Size	Optional	Config	N/A	Max concurrent connections from Summation. Default `10`. Set in the app; not part of the connector’s API field set.

The field names on the left are form labels; the API takes the keys in the fourth column. Sending host or database in a config object does not work, and because config accepts unknown keys, the connection is created and reports ACTIVE anyway. The failure surfaces later at connections test, as “Postgres database and username are required”, naming the labels, not the keys. Always test straight after creating.

SSL modes

Mode	What it does
`disable`	No SSL. Don’t use over the public internet.
`prefer`	Use TLS if the server offers it, otherwise fall back to plaintext; certificate not verified. The default when SSL Mode is left unset.
`require`	TLS on; certificate not verified.
`verify-ca`	TLS on; certificate verified against a trusted CA.
`verify-full`	TLS on; certificate verified and hostname checked. Recommended.

verify-ca and verify-full always require a CA bundle in CA Certificate, including with managed providers that use a well-known public root. Without one, the connection is created and reports ACTIVE, and connections test then fails with “Postgres CA certificate is required.” To get the right bundle, read the chain the server actually presents and take its root:

openssl s_client -connect <host>:5432 -starttls postgres -showcerts </dev/null

Paste that root PEM into CA Certificate (pg_sslrootcert, a secret). Verify it works on its own before sending it:

openssl s_client -connect <host>:5432 -starttls postgres \
  -CAfile ./root.pem -verify_hostname <host> </dev/null   # want: Verify return code: 0 (ok)

When verify-full fails, the tempting fix is dropping to require. Don’t. require encrypts the connection but verifies no certificate at all, so it succeeds instantly and silently gives up the protection you were configuring. Supply the CA instead.

Setup SQL

CREATE ROLE summation LOGIN PASSWORD '<strong-password>';

GRANT CONNECT ON DATABASE analytics       TO summation;
GRANT USAGE   ON SCHEMA public            TO summation;
GRANT SELECT  ON ALL TABLES IN SCHEMA public TO summation;

ALTER DEFAULT PRIVILEGES IN SCHEMA public
  GRANT SELECT ON TABLES TO summation;

Adding datasets

Source references use the form:

postgres:my_database.my_schema.my_table

Common problems

Error or symptom	Likely cause
`connection refused`	Wrong host/port, or your firewall doesn’t allow Summation’s egress IPs.
`SSL connection is required`	The server requires TLS. Set SSL Mode to `require` or stricter.
`server certificate ... does not match host name`	The cert’s CN/SAN doesn’t include the host. Fix the cert or use `verify-ca`.
`permission denied for relation ...`	Grant `SELECT` on the table to the Summation role.

Get started

Key concepts

Connectors

Agent integrations

What you’ll need

Where to find host/port for your provider

Form fields

SSL modes

Setup SQL

Adding datasets

Common problems

​What you’ll need

​Where to find host/port for your provider

​Form fields

​SSL modes

​Setup SQL

​Adding datasets

​Common problems

What you’ll need

Where to find host/port for your provider

Form fields

SSL modes

Setup SQL

Adding datasets

Common problems