For kitchen table startups that nevertheless deal in important data, having reliable managed PostgreSQL for much lower cost than AWS RDS would be awesome. The

For kitchen table startups that nevertheless deal in important data, having reliable managed PostgreSQL for much lower cost than AWS RDS would be awesome. The main thing I'm looking for in managed PostgreSQL isn't "installation" -- that's easy -- what I need is not to have to spend weeks of configuring and testing and drilling, to be reasonably confident that I won't lose customer data. I see DigitalOcean does PG standby servers, and daily backups, but I'm unclear on whether they're doing separate, say, WAL-based backups. The couple mentions I saw of "PITR" seemed to conflate that with the daily backups. There's a partial description of the UI, but it's still unclear: https://docs.digitalocean.com/products/databases/postgresql/how-to/restore-from-backups/ https://docs.digitalocean.com/products/databases/postgresql/... > In the Create a new cluster from a backup window that opens, choose whether you want to restore to the latest transaction available or choose a point in time, What's the "latest transaction available"? (Is it to moments before someone ripped the cables out of the storage server? Or is it the most recent daily backup, which might've been 23 hours ago?) > By default, the name is the original databases’ name appended with the date of the backup and the word “backup”, like originalname-aug-13-backup. I don't want to be trying urgently to recover the businesses of myself and my customers, and find myself asking design questions akin to "Why isn't this a UTC ISO date/timestamp?" but more like "Why are the backups done in such a way that they can't be restored for this ordinary failure scenario that just happened?" I don't see any technical reason that a cloud provider can't give enterprise DBA confidence at kitchen table startup rates, but I'd feel silly for assuming that they do.