PostgreSQL Connector

Use PostgreSQL as a source or destination. Replicate accessible tables into a supported destination, or load pipeline data into PostgreSQL.

SourceDestinationGold

Start for Free Source Documentation Destination Documentation

Evaluating against Fivetran? See how Supaflow handles PostgreSQL pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Load PostgreSQL into Snowflake

Dedicated pages for destination-specific setup, buyer questions, and Snowflake sync behavior.

PostgreSQL to Snowflake

Load PostgreSQL tables into Snowflake with primary-key backfills and streamed incremental sync.

View pipeline page

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Username/Password Authentication with SSL

Connect with database credentials over configurable SSL modes: disable, allow, prefer, require, verify-ca, or verify-full. Supports additional JDBC connection parameters.

Automatic Schema Discovery

Discovers the schemas, tables, columns, and primary keys visible to the connected database user. Schema metadata refreshes automatically on a configurable interval, from every run up to weekly.

Incremental Sync

Tracks a selected cursor column so subsequent runs fetch rows after the saved position. Full refresh remains available when a table has no reliable incremental cursor.

Source and Destination Roles

Use a read-only account with SELECT access for a PostgreSQL source. A PostgreSQL destination instead needs permission to create and update the target schema and tables.

Supported Objects

Database Objects

Tables

All tables the connecting user has SELECT permission on.

Schemas

All schemas the user has USAGE permission on (e.g., public, analytics, sales).

How It Works

Prepare your PostgreSQL database

Create a dedicated read-only user with CONNECT and SELECT privileges on target schemas. If your database has IP restrictions, add 18.214.240.61 to pg_hba.conf and ensure listen_addresses allows external connections.

Enter connection details

Provide the database host, port (default 5432), database name, username, and password. Configure SSL mode based on your security requirements.

Test and save

Click Test & Save to verify the connection. Supaflow runs a connectivity check and discovers available schemas, tables, and columns.

Use Cases

Replicate operational data to a warehouse

Sync PostgreSQL tables into Snowflake or another warehouse for analytics without running reporting queries against your production database.

Cross-database consolidation

Combine data from multiple PostgreSQL databases into a single warehouse for unified reporting across services.

Reverse ETL back to PostgreSQL

Write enriched or aggregated data from your warehouse back into PostgreSQL for use by operational applications.

Frequently Asked Questions

How do I connect Supaflow to an on-premises PostgreSQL database?

For production, deploy a self-hosted Docker Agent on a stable host inside the same private network as PostgreSQL. The agent connects to PostgreSQL over the private network and polls Supaflow over outbound HTTPS, so the database port stays private. For a quick proof-of-concept connectivity test, a temporary TCP tunnel can work; the linked SQL Server walkthrough demonstrates the network pattern, but you must use the PostgreSQL port and follow your PostgreSQL authentication and TLS requirements.

Deploy a self-hosted Docker Agent See the temporary TCP tunnel pattern

Which PostgreSQL versions are supported?

PostgreSQL 9.6 and higher. This includes managed services like Amazon RDS, Google Cloud SQL, Azure Database for PostgreSQL, and Supabase.

Can I use PostgreSQL as a destination?

Yes. Supaflow can load data from any supported source into PostgreSQL, including managed services like Amazon RDS, Google Cloud SQL, Azure Database for PostgreSQL, and Supabase. The target schema and tables are created automatically, so the destination user needs permission to create and write objects rather than read-only access.

Do I need to share my Supabase admin database password?

No. For Supabase projects, create a dedicated PostgreSQL database user for Supaflow and grant it permission to create and write the destination schema. Use that user's database credentials in Supaflow instead of your project admin password. Supabase Auth tokens and API keys are API credentials; destination loads need PostgreSQL privileges for schema creation, table writes, and schema evolution.

Do I need to whitelist an IP address?

If your database restricts inbound connections, add 18.214.240.61 to your firewall rules or pg_hba.conf. For cloud-hosted databases, add the IP in the networking settings of your provider.

Can I limit which tables are accessible?

Yes. Grant SELECT only on specific tables or schemas. The connecting user will only see objects they have permission to read.

Can I sync PostgreSQL views or foreign tables?

Not currently. The PostgreSQL source discovers and syncs tables only. If you need data from a view, materialize it into a table before syncing.

Does Supaflow support PostgreSQL CDC (Change Data Capture)?

Supaflow supports incremental sync using timestamp-based cursor fields. For full CDC with logical replication, contact us about our roadmap.

Can I replicate PostgreSQL to Snowflake natively?

Yes. The dedicated PostgreSQL to Snowflake page covers the source-to-destination workflow, supported sync modes, type handling, and deployment options in detail.

What about schema changes in my PostgreSQL database?

Supaflow detects schema changes automatically. New columns are added to the destination, type widening is applied, and new tables appear in schema discovery for you to enable.