alt Hacker NewsThe problem i see with this approach is that nearly nobody uses dumps as backups. I consulted Postgres for a few hundred customers and the amount of times that I saw dumps as Backup can probably be counted on two hands.
Does not help that the description reads like AI slop.
v1 is pg_dump only because it's the thing that every Postgres install can do natively, and the fastest way to get something really working and tested. Physical backups, pgBackRest specifically are already on the roadmap. One person on interviews doing this kind of testing was on plain dumps and moving off them, about 18 hours to restore versus 2 with a physical backup tool. I don't want to disagree here, I know dump-based isn't a great long term strategy. I will enhance the REAME, thank you for the feedback.