We have a billing database that uses a PostgreSQL backend, and our billing manager has insisted that we do backups hourly, because of how much work we'd lose from daily backups.
My inexperience at managing databases larger than a bunch of Wordpress sites is starting to show, since "make backups hourly" has turned into "why is our database so sloooow" as our billing database has grown. So in search of solutions to this problem, largely in the form of some kind of scheme where I replicate the database to another server that does the backups, I found this unique feature of Postgres. (Or at least, I can't find any such scheme for MySQL, which I'm more familiar with)
Is this what I'm looking for? Or is there a better solution to our problem? Are we going to lose any of our data should someone accidentally nuke a table or a large subset of our customers? Is it also a solution for "we borked the VM, or the hard drive failed"? How hard is it to restore our database to one particular point in time?