ahmadpiran

4 ms·

1.
by ahmadpiran 1mo ago
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
2.
by ahmadpiran 1mo ago
No worries at all. I take this to improve my working style. I appreciate you circling back to say this :)
3.
by ahmadpiran 1mo ago
One person I talked to had Veeam SureBackup running and still built a separate check for the database. As I know SureBackup proved the VM boots, but it doesn't know or care if your orders table has the right row count, or if a sequence
4.
by ahmadpiran 1mo ago
I don't have a good defense here, it's fair. But part of that was because of messy commit history and I wanted to have a clean commit history. Maybe it's not a good reason as well, but it was my real intention and my desire o
5.
by ahmadpiran 1mo ago
Fair, you're right. Thanks for the point. I used ai for a chunk of the build and writing. However, the actual work behind it wasn't AI-generated. I spent a few weeks interviewing people in r/devops and some compliance subs ab
6.
by ahmadpiran 1mo ago
Nobody disputes that backups need testing. Almost nobody actually does it, because there's no safe place to restore to and no time to build one. The people who do automate it usually end up with a cron job and a shell script that fails
7.
Show HN: Restoredrill – proves your Postgres backups restore(github.com)
50 points by ahmadpiran 1mo ago|23 comments
8.
Show HN: Restoredrill proves your Postgres backups restore(github.com)
2 points by ahmadpiran 2mo ago|0 comments