When faced with the alternative of loosing the entire database [1], loosing 410 transactions is usually preferable. Per second granularity gives you ability to

When faced with the alternative of loosing the entire database [1], loosing 410 transactions is usually preferable. Per second granularity gives you ability to restore as close to the fatal mistake (or poison pill transaction) as possible. After that, recovering transactions lost by the rewind can be really tricky (but not impossible). If the entire database got dropped, for example, it’s possible for the unwound writes to contain conflicting IDs. [1] https://about.gitlab.com/2017/02/10/postmortem-of-database-outage-of-january-31/ https://about.gitlab.com/2017/02/10/postmortem-of-database-o...