Notice of Obsolescence — the build
Yesterday David Steele announced that he is stepping away from pgBackRest. After thirteen years, the most widely-deployed dedicated backup tool in the Post…
Yesterday David Steele announced that he is stepping away from pgBackRest. After thirteen years, the most widely-deployed dedicated backup tool in the PostgreSQL ecosystem is no longer maintained. The current release, v2.58.0, is the last release. Steele asks that any forks pick a new name, which is — among other things — an act of professional courtesy from a maintainer who has clearly thought about how trust gets built and how it doesn’t get inherited. The announcement is restrained in the way these things often are. The implications are not. What actually happened For most of pgBackRest’s l
saved by
related reading
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- Databases in 2024: A Year in Review // Blog // Andy Pavlo - Carnegie Mellon Universitycs.cmu.edu
- Just Use Postgres for Everything | Amazing CTOamazingcto.com
- Blog — PlanetScaleplanetscale.com
- Why PostgreSQL Is the Bedrock for the Future of Datatigerdata.com
- The startup's Postgres survival guidehatchet.run
- How we migrated our PostgreSQL database with 11 seconds downtime – Government Digital Servicegds.blog.gov.uk
- Databases in 2025: A Year in Review // Blog // Andy Pavlo - Carnegie Mellon Universitycs.cmu.edu
- Schedule | POSETTE: An Event for Postgres 2024 - Citus Datacitusdata.com
- PgBouncer is useful, important, and fraught with peril - JP Camarajpcamara.com
- Nine ways to shoot yourself in the foot with PostgreSQLphilbooth.me