PostgreSQL
The PostgreSQL connector connects directly to one database over the Postgres wire protocol and reads its structure from information_schema. Discovery runs a small, fixed set of metadata queries and streams results in bounded batches — it never reads rows from your tables.
Connection settingsDirect link to Connection settings
| Field | Required | Notes |
|---|---|---|
host | Yes | Hostname or IPv4 literal. Schemes, paths, and raw IPv6 literals are rejected; for IPv6, use a hostname that resolves to an IPv6 address. |
port | No | Defaults to 5432. |
database | Yes | The database to discover — one database per connector. |
user | Yes | The login role the sync connects as. Grant it read access to the metadata you want cataloged. |
ssl | No | Defaults to true. |
password | Yes | Stored in Supabase Vault; decrypted only in the sync worker and never shown again after saving. |
Testing the connection runs a short-lived SELECT 1 probe under a strict deadline, so a wrong host or credential fails fast with a redacted message.
What gets discoveredDirect link to What gets discovered
- The connected database, as the catalog database.
- Its schemas. System schemas (
pg_catalog,information_schema,pg_toast) and temporary schemas are excluded. - Base tables and views in those schemas.
- Columns, with data type and nullability.
After discovery, use the connector's sync scope to pick exactly which schemas and tables are synced — see the connectors overview.
NetworkDirect link to Network
Metatate refuses to connect to private, loopback, or link-local addresses. The check runs against a literal IP you enter and against every address a hostname resolves to — if any resolved address is forbidden, the whole configuration is refused. The hostname is resolved once up front and the driver dials the vetted address directly, while TLS certificate verification stays bound to the hostname you entered. Your database must therefore be reachable at a public address; the connector cannot reach hosts inside a private network.