pgBackRest Is Dead? | Scaling Postgres 415

The sudden archiving of pgBackRest on April 27, 2026, has sent shockwaves through the PostgreSQL community, not because the tool failed, but because it was maintained by a single engineer—David Steele—for 13 years under Crunchy Data’s sponsorship. When Crunchy Data was acquired, funding vanished, and the project was left without a steward. This isn’t just a tool’s death—it’s a systemic failure in open source sustainability. The episode dissects why pgBackRest was so vital: it offered block-level incremental backups, encryption, S3/Azure/GCP support, and a custom protocol—features Postgres itself lacks. Now, with no official maintenance, the community faces a fork war or abandonment. But the deeper issue is structural: pgBackRest was a 'solo-maintained' project with no foundation backing, unlike CloudNativePG, which is in the CNCF sandbox and protected by vendor-neutral governance. The episode argues that open source doesn’t die—it gets unfunded—and calls for an umbrella organization, like the Apache Software Foundation, to shepherd critical infrastructure. Meanwhile, Postgres 19’s upcoming parallel auto-vacuum and tools like PG Weight Tracer signal progress, but they can’t fix the fragility of relying on one person’s dedication. The real takeaway? Sustainability isn’t a feature—it’s a necessity.