Two-way sync
Changes in PostgreSQL or TiDB instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Keep the same dataset live in both PostgreSQL and TiDB, so each workload runs on the engine that suits it.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
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 | |
|---|---|---|
| Views Read-side projections used to expose joined or filtered data to a sync. | Sequences Server-side ID generation relevant when external systems write rows. | |
| Materialized Views Precomputed result sets synced outward on a refresh schedule. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | |
| Schemas Namespaces that scope which tables a sync reads and writes. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | |
| Columns Field-level mapping targets; types are mapped to the connected system's field types. | Views Logical views for shaping reads before syncing outward. | |
| Primary and Unique Keys Used as match keys for idempotent upserts and conflict resolution. | Columns MySQL-compatible types mapped to fields in the paired system. | |
| JSONB Columns Hold semi-structured payloads such as nested SaaS objects or metadata. | Indexes Secondary indexes that keep incremental sync queries efficient. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every PostgreSQL–TiDB connection.
Changes in PostgreSQL or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever PostgreSQL or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single PostgreSQL or TiDB record.
Track your PostgreSQL ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between PostgreSQL and TiDB.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between PostgreSQL and TiDB: authenticate both systems, choose the objects to sync (such as PostgreSQL's Views and Materialized Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed PostgreSQL and TiDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom PostgreSQL–TiDB integration in-house.
Yes — Stacksync ships production-grade connectors for both PostgreSQL and TiDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on PostgreSQL: 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. On TiDB: Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the PostgreSQL side: Primary and Unique Keys, JSONB Columns, Sequences, Custom Types and Enums, plus custom fields where PostgreSQL exposes them. On the TiDB side: Sequences, Databases, Tables, Views. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for PostgreSQL and TiDB.