Pgbackrest is no longer being maintained
The popular PostgreSQL backup and restore tool, pgBackRest, is ceasing maintenance after thirteen years. Its creator cites an inability to secure financial sponsorship to continue the extensive work required. This news has sparked significant discussion on Hacker News about the sustainability of critical open-source projects and the challenges maintainers face.
The Lowdown
pgBackRest, a highly regarded PostgreSQL backup and restore solution, has announced its discontinuation of maintenance. The creator, dwsteele, shared a "Notice of Obsolescence" on GitHub, stating that after thirteen years, the project is no longer viable due to a lack of financial support.
Key aspects and reasons for its popularity included:
- Comprehensive Features: pgBackRest offered parallel backup/restore, support for local or remote operations, multiple repositories, and various backup types (full, differential, incremental, block-level).
- Robustness and Integrity: Emphasizing backup integrity, it included checksum calculations, page checksum validation, and durable operations with file/directory level fsync.
- Advanced Capabilities: Features like backup resume, streaming compression, delta restore, parallel WAL push/get, and support for tablespaces and object stores (S3, Azure, GCS) made it a powerful tool.
- Maintainer's Dilemma: After Crunchy Data, a former sponsor, was sold, the maintainer struggled to find a new position that would allow continued work on pgBackRest or secure sufficient sponsorship to sustain the project.
- Call for Renaming: The creator explicitly requested that any future forks of the project adopt a new name to avoid confusion and ensure a clear distinction in maintainership.
The cessation of maintenance for such a critical and widely used tool highlights the ongoing challenges of funding and sustaining essential open-source infrastructure.
The Gossip
The End of an Era: PgBackRest's Departure
Many users expressed shock and sadness over the discontinuation of pgBackRest's maintenance, widely considered a leading PostgreSQL backup solution. They lauded its features, reliability, and how it simplified complex backup and restore operations for their production databases. Several users had just recently adopted or were about to adopt it, making the news particularly impactful, with some feeling the timing was almost comically bad for them.
Open Source: Pay to Play or Pray?
A dominant theme revolved around the ongoing struggle for open-source project sustainability. Commenters debated whether users, especially commercial entities, should contribute financially to critical tools they rely on. The maintainer's inability to secure sponsorship after losing corporate backing was seen as a cautionary tale about maintainer burnout and the difficulty of monetizing essential open-source work. Some suggested alternative licensing models (e.g., tiered pricing), while others lamented the 'curse of OSS,' where passionate creators eventually give up due to lack of support.
The Search for a Successor: Alternatives & Comparisons
Immediately following the news, many users scrambled to identify viable alternatives to pgBackRest. WAL-G and Barman were frequently mentioned as primary contenders, with users discussing their relative strengths, weaknesses, and feature parity, particularly concerning object storage support and point-in-time recovery. The clear documentation of pgBackRest was noted as a reason some chose it over alternatives, highlighting a new challenge for those migrating.
Forking & Naming Conventions
The maintainer's request for forks to use a new name sparked discussion. Some defended this as a reasonable request to prevent confusion and protect the original maintainer's reputation from future changes, citing 'pgbackrest-ng' as a good example. Others debated the concept of 'gatekeeping' a name for an MIT-licensed project, contrasting it with the practical need for clear lineage and trust in critical infrastructure software, especially to avoid malicious forks or supply chain attacks.
Humorous Hyperbole & AI Hype
Amidst the serious discussion, some comments injected levity or sarcasm. Jokes about 'vibe-coding' backups or applying the 'AI-driven' label to attract instant funding highlighted the current tech landscape's trends and absurdities, albeit in a dark humor sort of way given the context of the story. There was also a humorous comment about PostgreSQL eventually building in its own backup solutions, to which a user clarified what's actually available.