Postgres table — `postgres`

Polls a table incrementally, one event per new/changed row. The cursor tracks a monotonic column (an autoincrement id, or updated_at); an entity column (e.g. tenant_id) becomes the key via a primary label. Your application’s source-of-truth data in the timeline. Supports discovery: given the connection URL it lists the tables it can see, then reads the chosen table’s columns to propose the cursor and labels.

Prerequisites: a Postgres reachable from the NavFlow host. The driver ships with NavFlow — no extra to install.

Set up

Agent

Ask a connected agent:

Use navflow to ingest the orders table at <dsn>, keyed by tenant_id.

The agent calls discover_source (lists tables, then proposes the cursor and labels from the columns), test_source (dry-run — fetches sample rows), then create_source. Walkthrough: Connect a Postgres table.

Console

Sources → Add source → Postgres. Enter the Connection URL (dsn) and Discover — it lists the tables it can see; pick one, and it proposes the cursor, entity key and labels from the columns. Choose which columns to pull (all by default), then save.

YAML / API


- name: orders
  connector: postgres
  poll: 10s
  config:
    dsn: postgresql://user:pass@host:5432/appdb
    table: orders
    cursor_column: updated_at
    columns: id,tenant_id,status,amount,updated_at   # empty = every column
    labels:
      - { name: tenant_id, field: tenant_id, primary: true }
      - { name: status, field: status }

Or POST /api/sources with the same object. The dsn is stored as a secret (redacted in the API, omitted from catalog exports).

Configuration

field	type	description
`dsn`*	string · secret	`postgresql://user:pass@host:port/dbname` — this source’s connection URL
`table`*	string	table to poll, e.g. `orders` or `public.orders` (Discover lists the tables)
`cursor_column`*	string	column that only ever grows — an `id` (inserts) or `updated_at` (also updates). Discover picks it
`columns`	string	comma-separated columns to pull (empty = every column). The cursor / key / time columns are always included
`time_column`	string	timestamp column for `event_time` (default: the cursor if it’s a timestamp, else ingest time)
`limit`	number	rows to fetch per poll
`text_template`	string · advanced	optional `str.format` template over the row, e.g. `'{tenant_id}: {status} ${amount}'`

database and table are also available as label fields (from config), regardless of which columns you pull.

Verify

Open the source: Recent events shows rows on the next poll; Fields reports each column’s coverage — use it to confirm the key column is reliably present.

Postgres table — postgres