Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.summation.com/llms.txt

Use this file to discover all available pages before exploring further.

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

ProviderWhere to look
Amazon RDS / AuroraRDS console → your DB instance → Connectivity & securityEndpoint and port. See Connecting to a DB instance.
Google Cloud SQLCloud SQL console → your instance → Connections. See About connection options.
Azure Database for PostgreSQLAzure portal → your server → Overview. See Connect with Azure CLI.
SupabaseProject dashboard → Project SettingsDatabaseConnection info. See Connect to Postgres.
NeonProject dashboard → Connection Details. See Connect to your database.

Form fields

FieldRequiredStored asNotes
HostYesConfigDNS name or IP, e.g. db.example.com.
PortYesConfigDefault 5432.
DatabaseYesConfigThe Postgres database name (not a schema).
UsernameYesConfigLogin role.
PasswordYesSecret
SSL ModeOptionalConfigOne of disable, require, verify-ca, verify-full. Default verify-full. See SSL Mode descriptions.
Root Certificate PathOptionalConfigPath to a CA bundle for verify-ca / verify-full. See SSL Client File Usage.
Connection Pool SizeOptionalConfigMax concurrent connections from Summation. Default 10.

SSL modes

ModeWhat it does
disableNo SSL. Don’t use over the public internet.
requireTLS on; certificate not verified.
verify-caTLS on; certificate verified against a trusted CA.
verify-fullTLS on; certificate verified and hostname checked. Recommended.
If your provider uses a self-signed CA, supply the bundle in Root Certificate Path. Most managed Postgres providers work with verify-full out of the box.

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 symptomLikely cause
connection refusedWrong host/port, or your firewall doesn’t allow Summation’s egress IPs.
SSL connection is requiredThe server requires TLS. Set SSL Mode to require or stricter.
server certificate ... does not match host nameThe 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.