Backups, PITR, read replicas & cost traps
Someone on the team runs a migration script against production with a WHERE clause that doesn't match what they thought, and half of DevLog's posts are gone. The question that decides whether this is a bad afternoon or a resume-updating event is one you should have answered BEFORE it happened: what's your actual recovery point, how destructive is getting there, and does the read replica everyone's been pointing reads at help even slightly? (It doesn't.)
try to break it
you drive.
Blue dots = daily backups. Green band = a PITR window covering the whole week.
Nearest restore point is the backup taken at the start of day 3. You recover the DELETE — and also lose every legitimate write made since then: ~9.6h of real data, gone too.
Restore to the second before the DELETE ran. ~0 data lost. The restore itself is still destructive and takes the whole project down while it runs — there is no per-table undo.