pgBackRest, a 13-year-old open-source PostgreSQL backup and restore tool, is EOL after its maintainer failed to secure post-Crunchy Data sponsorship or a new role.
Key Takeaways
The project reached v2.58.0 before shutdown; features include parallel backup/restore, block-level incremental backups, WAL archive management, and S3/Azure/GCS object store support.
Maintainer David Steele built pgBackRest through Crunchy Data sponsorship; after Crunchy was sold, he could not find sponsorship or employment tied to continuing the work.
Rather than sporadic unmaintained releases, the repo was hard-stopped with a notice of obsolescence; forks are permitted but must use a new name.
Current sponsor Supabase is listed; the project’s only remaining backer, which signals how thin the commercial support base was at shutdown.
Block-level backups, delta restores, and async WAL push/get represent features beyond basic pg_dump that teams relying on this will need to replicate in any successor.
Hacker News Comment Review
Commenters expressed surprise the maintainer did not pursue a formal handoff or successor search, given 3.8k GitHub stars and an active contributor base.
No alternative tools were named in the thread; the question of what replaces pgBackRest for teams using autobase or self-managed Postgres remains open.
One commenter sarcastically noted the irony of teams potentially “vibe-coding” production database backup solutions, reflecting broader anxiety about critical infra depending on single-maintainer open source.
Notable Comments
@hleszek: Questions why a successor search was skipped given the repo’s star count and contributor history.
@timwis: Notes pgBackRest may underpin backup infrastructure in RDS and Cloud SQL, raising the stakes for the shutdown.
