> Of course, Thou Shalt Have Backups, but it's not exactly a frictionless experience if you fry things and have to go back to them. I do wonder how much of thi

> Of course, Thou Shalt Have Backups, but it's not exactly a frictionless experience if you fry things and have to go back to them. I do wonder how much of this is because of, specifically, PostgreSQL not having enough "market" penetration. For a very long time, it's had very good unclean-shutdown resilience with the way it does its write-ahead logs and has even had point-in-time-recovery (using those same WALs, just stored longer) for several years. Combine that with a snapshotting filesystem, and that would seem like a pretty low amount of friction for recovery, without even having formal backups. If your database is big enough, you need a certain amount of performance out of it, or you need it to be a recent enough copy [1] of the production data (which likely means "all of the above"), then it does start to get legitimately challenging. [1] or, worse, something ETL'ed (anonymization comes to mind)