Skip to main content
Telara

Integrations / PostgreSQL

PostgreSQL logo

PostgreSQL

PostgreSQL relational database management system

Basic auth
Indexes
Actions

What Telara does

Capability matrix

Before you connect

Prerequisites

A Postgres instance Telara can reach.
A dedicated role that can connect to the database Telara should see. Prefer that over a superuser.

Vendor setup

Get the credential

1
Create a login
Create a role with CONNECT on the target database and the least privilege needed to read the catalogs Telara uses.
2
Paste in Telara
Settings → Integrations → PostgreSQL. Enter host, port, database name, username, and password. Turn on TLS if the server requires it.

In Telara

Connect in Telara

Basic auth

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Username
  • Password
  • Host
  • Port
  • Database
  • Ssl Mode

Knowledge

What gets indexed

ResourceCoverage
SchemaPartial — not every record the vendor holds is synced
TablePartial — not every record the vendor holds is synced
ViewPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
SchemaUp to 1 dayRemoved records disappear on the next full sync
TableUp to 1 dayRemoved records disappear on the next full sync
ViewUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Schema, Table, View.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Network path is the usual failure (security group, private IP, or a hostname that only resolves inside the VPC).
A role that can log in but cannot see catalogs produces an empty schema list, not an auth error.