David Steele just posted a notice of obsolescence on pgbackrest.org . After thirteen years of building what became the default PostgreSQL backup tool, he's stepping away. The reason isn't burnout or a better offer. It's economics. Since Crunchy Data was sold, Steele hasn't found a role or sponsorship that would let him maintain pgBackRest full-time. So instead of doing the work poorly, he chose a hard stop. If you run PostgreSQL in production, this should grab your attention. Choosing the right PostgreSQL backup tool is one of those decisions that feels boring until you need a restore at 3 AM. For a lot of teams, pgBackRest was the answer they never questioned. That just changed. I've managed PostgreSQL clusters handling hundreds of millions of rows, and I've had to execute point-in-time recoveries under real pressure. The tool you pick for backups is not a checkbox exercise. It's the difference between a 20-minute recovery and losing a weekend (or worse).…