Skip to main content
Each row becomes one bucket object. The same connection also backs the sql_lookup retriever stage.

Overview

A PostgreSQL connection serves two paths:
  • Sync. Rows from a table land in a bucket as JSON objects, with incremental sync via a watermark column.
  • Lookup. The sql_lookup retriever stage enriches documents mid-pipeline.

Prerequisites

  • PostgreSQL 12 or later.
  • A role with CONNECT on the database and USAGE on the schema.
  • SELECT on every table you sync or query.
  • Network access from Mixpeek to the server.

Configuration

Connection-level fields

Sync-level fields

source_path accepts one or two dot-separated parts. Three or more returns a validation error.

Setup

1

Create a read-only role

2

Create the storage connection

3

Sync a table

Incremental sync

Set incremental_column to a TIMESTAMP or DATE column. Mixpeek records the highest value it has read and filters the next run to rows above it. Set primary_key_columns so object IDs stay stable across runs. Without it, a re-read can create a second object for the same row.

SQL Lookup stage

Enrich documents from a SQL source inside a retriever.

Snowflake

Warehouse connection with the same two paths.