Features¶
PGSync focuses on reliability, low overhead, and clean documents for search.
Highlights¶
| Feature | Description |
|---|---|
| Multi-Database Support | Works with PostgreSQL (9.6+), MySQL (5.7+), or MariaDB (10.5+) |
| Low Overhead | Negligible impact on database performance |
| Transactional Consistency | Only committed writes indexed; operations applied in commit order |
| Fault Tolerant | No data loss on crashes; resumes from last checkpoint |
| Native JSON Path | Returns data directly as PostgreSQL JSON for speed |
| Composite Keys | Supports composite primary and foreign keys |
| Deeply Nested Documents | Arbitrary depth of related entities supported |
| Customizable Structure | Tailor documents to your index and query needs |
Details¶
Consistency¶
- Only committed transactions appear in Elasticsearch/OpenSearch
- Operation order (insert → update → delete) is preserved based on commit order
Reliability¶
- Designed to avoid data loss if a process crashes or the network drops
- Recovery resumes from the last successful checkpoint
Data Modeling¶
- Composite primary and foreign keys supported
- Arbitrary-depth relationships (one-to-one, one-to-many, through tables)
- Extract and map PostgreSQL JSON fields to top-level document fields
Performance¶
- Builds documents directly from PostgreSQL JSON to minimize transformation overhead
Compatibility¶
| Database/Service | Minimum Version |
|---|---|
| PostgreSQL | 9.6+ |
| MySQL | 5.7+ |
| MariaDB | 10.5+ |
| Elasticsearch | 6.3.1+ |
| OpenSearch | 1.3.7+ |
More destinations
Beyond search: PGSync ClickHouse streams
PostgreSQL into ClickHouse for real-time analytics, and
PGSync Pro adds semantic & hybrid search, the same
schema.json and CLI.