- Source
- Databases
- Generally available
Move Postgres data anywhere it matters.
Replicate Postgres data to the warehouse or AI app you use.
Source
Postgres

Snowflake
BigQuery
Postgres
Databricks
Claude
- Destinations
- 50+
- Certified support
- 3.8.9
Overview
What is the Airbyte Postgres connector?
The Airbyte Postgres connector extracts data from Postgres and loads it into 50+ destinations such as Snowflake, BigQuery, Databricks or Postgres, with scheduled sync. It publishes tables and events you can select per connection.
- 01
Sync to your warehouse
Land Postgres data in 50+ destinations on a schedule you control.
- 02
One authorization
Authenticate Postgres once and Airbyte keeps every scheduled sync running on it.
- 03
Cloud or self-hosted
Run the Postgres connector on Cloud, OSS, Hybrid.
Setup
Live in ten steps
Open your PostgreSQL database and create a new user with the necessary permissions to access the data you want to replicate.
Obtain the hostname or IP address of your PostgreSQL server and the port number it is listening on.
Create a new database in PostgreSQL that will be used to store the replicated data.
Obtain the name of the database you just created.
In Airbyte, navigate to the PostgreSQL source connector and click on "Create Connection".
Enter a name for your connection and fill in the required fields, including the hostname or IP address, port number, database name, username, and password.
Test the connection to ensure that Airbyte can successfully connect to your PostgreSQL database.
Select the tables or views you want to replicate and configure any necessary settings, such as the replication frequency and the replication method.
Save your configuration and start the replication process.
Monitor the replication process to ensure that it is running smoothly and troubleshoot any issues that arise.
Configuration fields
| Field | Type | Description |
|---|---|---|
| database* | string | The name of the database to connect to. |
| host* | string | Hostname of the database. |
| port* | integer | Port of the database. Defaults to 5432. |
| replication_method* | object | Configures how data is extracted from the database. |
| tunnel_method* | object | Whether to initiate an SSH tunnel before connecting to the database, and if so, which kind of authentication to use. |
| username* | string | The username which is used to access the database. |
| check_privileges | boolean | When this feature is enabled, during schema discovery the connector will query each table or view individually to check access privileges and inaccessible tables, views, or columns therein will be removed. In large schemas, this might cause schema discovery to take too long, in which case it might be advisable to disable this feature. |
| checkpoint_target_interval_seconds | integer | How often (in seconds) a stream should checkpoint, when possible. |
Hybrid deployment
Sovereign by architecture, not by policy.
The data plane runs in your environment. Records, credentials and keys stay with you; the control plane only receives configuration and job metadata.
- Cloud
- OSS
- Hybrid
Your environment
Airbyte control plane
FAQ
Postgres connector questions
What data can I sync from Postgres with Airbyte?
The Postgres connector syncs the tables and events published in Airbyte docs.
Does the Postgres connector support incremental sync?
Check the Airbyte docs for the sync modes the Postgres connector supports.
Where can I run the Postgres connector?
Run the Postgres connector on Cloud, OSS, Hybrid. Hybrid deployments keep the data plane in your environment while the control plane orchestrates syncs.
Didn't find your answer? Talk to sales
Start syncing Postgres in minutes.
Free 14-day trial. No credit card needed.