Skip to content

Glossary

The words the app and these pages use, each with the page that says more. Where the app pairs its own word with PostgreSQL’s (a change bookmark (replication slot)), both are given.

A secret a program sends to call the API as your account, read only or full. API keys.

What a pipeline that reads the change log keeps on your PostgreSQL database: its place in the change log. While it exists, your database keeps every change written after that place, even while nothing reads it. You create it yourself, with the statement the pipeline shows, right before the pipeline starts. Set up a PostgreSQL source.

The record PostgreSQL keeps of every change it writes (its write-ahead log). A pipeline reads it through logical replication, so every insert, update and delete arrives as it happens. A PostgreSQL source.

The steps that check a source or destination can be used, in the order a connection is made. Each step passes, passes with a warning, or fails with a message; a step after a failed one is not run. The connection test.

The warehouse or database a pipeline writes into: Snowflake or PostgreSQL. Snowflake, PostgreSQL.

On an API error, whose side the cause is on: customer, upstream, ours or undetermined. The REST API.

A value a program sends with each change it asks the API for, so a retry of the same request to the same path is not done twice. The REST API.

What copies tables from a source to a destination and keeps them current: each table once, then what changes after that. A pipeline’s tables.

A small program you run beside a database that has no public address; it connects out to us, so you open no inbound port. In preview and off by default: Proxy agents says what exists today.

The PostgreSQL publication that names which tables’ changes your database sends to a pipeline. The pipeline shows the statements that make it. Set up a PostgreSQL source.

A way to read a PostgreSQL source with no change log: each sync reads the rows that changed since the last. It does not see rows deleted in your database. Reading PostgreSQL by queries.

Copying some or all of a pipeline’s tables again. Sync modes and re-sync.

The identifier of one API request, in every answer’s X-Request-Id header and every error’s request_id. The REST API.

A pipeline’s work from one start to its end, listed in the run history with its own page. History, runs and the overview.

What your pipelines read from: a PostgreSQL database, or your account’s own history (the history export). A PostgreSQL source, Exporting your account’s history.

One of four ways a table is written into your destination, chosen per table: soft delete (soft_delete), live (live), history (history) or append-only (append). A table’s sync mode says what each one does.

Your account’s prepaid balance, which a day’s usage is charged against. Usage and billing.