Skip to main content
Connect Datawise to Postgres to enable Schema Radar detection and warehouse-level lineage.

Prerequisites

  • A Postgres user with SELECT privileges on information_schema and on the tables and views you want Datawise to track.
  • The hostname (or IP) and port for your Postgres instance.
  • The database name you want to connect.
Create a dedicated read-only Datawise user in Postgres rather than using an existing account.

Required Permissions

Datawise only reads schema metadata and does not access the data in your tables. Grant access only to the schemas you want Datawise to monitor. You can use the allow and deny pattern filters in the connector form to further control what gets ingested.
Option 1: All schemas (easiest, good for initial setup)
Option 2: Specific schemas only (recommended for production)
For production environments, use Option 2. Grant Datawise access only to the schemas you want monitored. This follows the principle of least privilege and limits Datawise’s footprint to exactly what your team has decided to track. You can always add more schemas later by running additional GRANT statements.

Connection Setup

Go to Connectors, click Add Connector, and select Postgres.

Required Fields

Filters

Patterns use glob syntax (e.g., prod_*). Leave all fields empty to ingest everything the user has access to.

Settings

Schedule

Testing the Connection

If the test fails, check:
  • That the hostname and port are reachable from Datawise. If your Postgres instance is behind a VPC or firewall, contact support for the current Datawise IP allowlist range.
  • That the user exists and the password is correct.
  • That the user has been granted CONNECT on the target database.

After Connecting

  • Tables and views from the connected schemas appear in Data Assets.
  • Schema Radar begins detecting schema changes on your configured schedule.
  • Lineage from Postgres populates when dbt Cloud is also connected and targeting the same Postgres instance.