PostgreSQL Collected Data

This page describes what Sifflet imports from your PostgreSQL database once the PostgreSQL source is connected.

Imported Assets

Sifflet imports the following objects from the schemas selected in the source scope:

• Tables, including the individual partitions of partitioned tables
• Views

Collected Metadata

For each table and view, Sifflet collects:

• Name and schema
• Description (the comment set with COMMENT ON TABLE)
• Columns: name, data type, nullability, default value, size, and description (the comment set with COMMENT ON COLUMN)

Lineage

Sifflet doesn't extract lineage between tables inside PostgreSQL (from query logs or view definitions).

PostgreSQL tables appear in lineage when other integrations reference them, for example BI tools, dbt, or data pipelines. Sifflet links these assets when the host, port, and database configured in the other tool match the PostgreSQL source.

Data Freshness

Sifflet refreshes the PostgreSQL metadata on the source schedule. See Integrations Management for the default frequency and scheduling options.

Limitations

• Materialized views, foreign tables, and parent partitioned tables are not imported. The partitions of a partitioned table are imported as tables.
• The Freshness (Update Time Gap) monitor, which relies on update times from table metadata, is not available for PostgreSQL.

Data Exposure

Sifflet stores metadata and monitor results. Some features read and display row-level data from your tables: data preview and the failing rows of monitors. See Security for details on the data that Sifflet accesses and stores.