pgxbackup: Continuity Support for pgBackRest

A quiet software handoff somehow turned into comment-section theater. PostgreSQL backup tool pgBackRest — basically the thing many companies trust to save their data when disaster strikes — is getting a continuity fork from PGX called pgxbackup. The company says it’s stepping in because maintenance has slowed, and it wants to keep the tool working, secure, and compatible with future PostgreSQL releases. It’s also honoring the original creator’s request not to keep using the old name. Sensible, respectful, boring... right? Not on the internet.

The strongest reaction was a blunt one: “Why not hire the original author?” That instantly reframed the whole announcement from “nice stewardship” to “wait, what happened behind the scenes?” It’s the kind of one-line comment that makes everyone lean forward. Was this the obvious solution? Was it impossible? Nobody knows from the post alone, which only made the vibe more suspicious and spicy.

Then the thread swerved into a totally different mini-drama: AI commit credit. One commenter groaned about seeing Claude named in commits everywhere, calling it a possible marketing gimmick and saying transparency is good, but not necessarily on every single change. So yes, a story about backup software somehow became a debate about whether AI is a helpful assistant or an attention-seeking co-worker who insists on signing the group project. In other words: classic tech community behavior — a rescue story up front, and in the comments, a pile-on about authorship, optics, and vibes.