ankane/pgsync

Sync data from one Postgres database to another

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 20th, 2026
Created on December 8th, 2015
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 219
Total Stargazers: 3,474 (+0)
Total Subscribers: 34 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 539 days
Stale 30+ days: 5
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

pgsync is a command-line tool that syncs data from one Postgres database to another.

The tool addresses the problem of keeping multiple Postgres databases in sync, whether for development environments, testing, or data replication workflows. It works by connecting to source and destination databases and transferring data while handling the complexities of schema differences, foreign key constraints, and data consistency. The approach allows developers to specify which tables to sync and manages the synchronization process automatically.

The tool suits developers who need to replicate production data to development or staging environments, or who maintain multiple database instances that need periodic synchronization. It works well for teams that want a straightforward way to keep databases aligned without writing custom migration scripts. Anyone considering adoption should know that pgsync is designed for Postgres specifically and handles the nuances of that database system, including constraint management and data type handling.

The project shows consistent maintenance with regular updates addressing user-reported issues and feature requests. Development activity demonstrates responsiveness to community feedback, with fixes and improvements being incorporated steadily. The codebase remains actively refined based on real-world usage patterns and edge cases encountered by users.