Skip to content
Database

PostgreSQL to TiDB integration — real-time, two-way sync

Keep PostgreSQL and TiDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect PostgreSQL and TiDB

Keep PostgreSQL and TiDB synchronized in real time, across engines, regions, or services, in one or both directions.

Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.

Stacksync syncs tables or collections between PostgreSQL and TiDB continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.

Common use cases

  • 01 Expose SaaS objects (CRM contacts, ERP invoices, support tickets) as Postgres tables that internal tools can query and join
  • 02 Let an application write to its own database and have those rows appear as records in business systems in near real time
  • 03 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics
  • 04 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas

Common sync patterns

Cross-engine sync

Keep the same dataset live in both PostgreSQL and TiDB, so each workload runs on the engine that suits it.

Migration with zero-downtime cutover

When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.

Shared reference data between services

Services that own separate databases stay consistent on the records they share, without a custom replication layer.

What you can sync between PostgreSQL and TiDB

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

PostgreSQL objects TiDB objects How this pairing syncs
Tables The primary sync target; rows map one-to-one to records in connected SaaS systems. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Views Read-side projections used to expose joined or filtered data to a sync. Views Logical views for shaping reads before syncing outward. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Columns Field-level mapping targets; types are mapped to the connected system's field types. Columns MySQL-compatible types mapped to fields in the paired system. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Sequences Generate surrogate keys for rows created by inbound syncs. Sequences Server-side ID generation relevant when external systems write rows. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Primary and Unique Keys Used as match keys for idempotent upserts and conflict resolution. Indexes Secondary indexes that keep incremental sync queries efficient. Primary and Unique Keys is specific to PostgreSQL and Indexes to TiDB — each maps to any object or custom field on the other side.
JSONB Columns Hold semi-structured payloads such as nested SaaS objects or metadata. Databases MySQL-style schemas addressed by any MySQL-compatible client. JSONB Columns is specific to PostgreSQL and Databases to TiDB — each maps to any object or custom field on the other side.

How changes propagate between PostgreSQL and TiDB

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

PostgreSQL TiDB Sub-second propagation

DetectionChanges in PostgreSQL are captured at the source via change data capture — no polling loop against its API. Logical replication (wal_level = logical) for change data capture via the "Postgres" connector.

DeliveryEach detected change is applied to TiDB as a row-level write, with types converted between the two schemas.

TiDB PostgreSQL Sub-second propagation

DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.

DeliveryEach detected change is applied to PostgreSQL as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • PostgreSQL: No API rate limits; throughput is bounded by connection limits, instance resources, and replication slot throughput.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with PostgreSQL ⇄ TiDB

Connect PostgreSQL and TiDB for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every PostgreSQL–TiDB connection.

Real-time

Two-way sync

Changes in PostgreSQL or TiDB instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever PostgreSQL or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single PostgreSQL or TiDB record.

Observability

Monitoring

Track your PostgreSQL ⇄ TiDB sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between PostgreSQL and TiDB.

How the PostgreSQL and TiDB connectors work

PostgreSQL

Integration surface
SQL wire protocol (PostgreSQL frontend/backend protocol)
Authentication
Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user
Change detection
Logical replication (wal_level = logical) for change data capture via the "Postgres" connector; database triggers (TRIGGER grant + stacksync_logging schema) via the trigger-based "Postgres Heroku" connector where
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits, instance resources, and replication slot throughput
PostgreSQL setup guide

TiDB

Integration surface
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Capabilities
read · write · CDC
Rate limits
Throughput scales with cluster size rather than fixed API quotas
How it works

How to connect PostgreSQL to TiDB — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate PostgreSQL and TiDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    PostgreSQL connected
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the PostgreSQL and TiDB objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · PostgreSQL ⇄ TiDB
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    PostgreSQL TiDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

PostgreSQL and TiDB integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 392 integrations available for PostgreSQL and TiDB.

Popular · 8 of 392
All PostgreSQL integrations All TiDB integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own