We have found that large production databases do not appreciate having frequent full SQL dumps taken from them. We offer an automatic daily snapshot option because we believe that for a production database it's really not wise to take dumps more frequently than that, though there's nothing stopping you from rolling your own.
You can set up Point In Time Recovery (PITR), and replay recovery logs. It's not clear from Heroku's pages whether their solution is set up that way.
It sounds like their solution is set up that way.
From https://postgres.heroku.com/#protect : "Every change to your data is written to write-ahead logs, which are shipped to multi-datacenter, high-durability storage. In the unlikely event of unrecoverable hardware failure, these logs can be automatically 'replayed' to recover the database to within seconds of its last known state."
It sounds like their solution is set up that way.
I think the question is whether the customer will be able to perform a point in time recovery, and what the size and resolution of the backlog is.
Not yet.
Thank you for that clarification.
I'm sorry, but daily backups are not only for high availability, but also for point in time recovery.
What if $dev drops the user table by mistake ? Do they provide backup for that ?