Pgbackrest is no longer being maintained (github.com)

Article summary

The pgBackRest project, a reliable backup and restore solution for PostgreSQL, is no longer being maintained. The project's maintainer has been unable to secure sufficient sponsorship to continue working on the project. pgBackRest has been a popular and widely-used tool, with over 3.8k stars on GitHub. Its discontinuation may leave users looking for alternative backup solutions.

Main themes

• pgBackRest discontinuation
• PostgreSQL backup solutions
• open-source maintenance
• sponsorship and funding
• project archiving
• alternative backup tools
• maintainer responsibility

What commenters say

• Some commenters express sadness and appreciation for the project's past contributions, while others discuss potential alternatives and the challenges of finding a suitable replacement.
• There is debate about whether the project should be archived or if a new maintainer should take over, with some arguing that allowing a new maintainer could lead to confusion or supply chain attacks.
• The responsibility for maintaining critical open-source software is discussed, with some arguing that it is unfair to expect maintainers to work for free, while others suggest that users who care about the project should step up to support it.
• Some commenters mention specific alternative backup tools, such as WAL-G and Barman, and share their experiences with these tools.
• The issue of sponsorship and funding for open-source projects is raised, with some commenters expressing frustration that critical projects like pgBackRest are not receiving the support they need.
• There is also discussion about the potential risks and challenges of forking the project and creating a new version with a different maintainer.
• The importance of having a clear and sustainable plan for maintaining critical open-source software is emphasized, to avoid disruptions and ensure continuity.
• Some commenters suggest that the project's maintainer has made the right decision in archiving the project, rather than risking potential problems with a new maintainer.