xataio/pgroll

PostgreSQL zero-downtime migrations made easy

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 25 minutes ago
Added to GitGenius on September 10th, 2026
Created on June 22nd, 2023
Open Issues & Pull Requests: 99 (+0)
GitHub issues: Enabled
Number of forks: 154
Total Stargazers: 6,576 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.1 days
Mean response time: 34.6 days
90th percentile: 93.0 days
Tracked items: 145

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 78% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 3% of issues opened in the past year have been closed. Three people close 73% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 82
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 538 days
Stale 30+ days: 81
Stale 90+ days: 77

Recent activity

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

Top labels

  • enhancement (35)
  • bug (26)
  • breaking-changes (12)
  • good first issue (11)
  • sql2pgroll (7)
  • documentation (6)
  • hacktoberfest (4)
  • help wanted (4)

Detailed Description

pgroll is a tool for performing zero-downtime schema migrations on PostgreSQL databases.

The problem pgroll solves is that standard PostgreSQL migrations typically require locking tables, causing downtime during schema changes. The tool enables developers to modify database schemas without interrupting application traffic by managing the complexity of coordinating schema changes across multiple application versions. It works by automating the orchestration of migration steps that can run safely while the database remains accessible, allowing old and new code to coexist during the transition period.

Teams should adopt pgroll when running production PostgreSQL systems where downtime during deployments is unacceptable. It suits applications with strict availability requirements or those handling high transaction volumes where even brief locks would cause noticeable service degradation. The tool is particularly valuable for teams managing large tables or complex schema changes that would normally require extended maintenance windows. It is less critical for development environments, staging systems, or applications that can tolerate scheduled downtime during deployments.

The project shows active development with regular commits addressing bug fixes and feature enhancements. The maintainers respond to issues and pull requests, indicating ongoing engagement with users. The codebase receives updates that improve reliability and expand migration capabilities. The project maintains documentation and examples that help users understand how to structure their migrations for zero-downtime execution.