The relevant bit of the article, if you are not familiar with eg git bisect: "The next day, you noticed your mistake and discovered that you deleted all users

The relevant bit of the article, if you are not familiar with eg git bisect: "The next day, you noticed your mistake and discovered that you deleted all users from the table instead of Alice. Unfortunately, you are not sure when exactly the query finished executing and rolling back to an arbitrary date is not an option. Since Neon offers the ability to create point-in-time branches, you can generate a sequence of branches that include past data in chronological order between two LSNs. You can then go through this list of branches and accurately determine when the disaster occurred." More generally a lot of recovery scenarios involve investigating to find when and what went wrong, which can be prohibitively hard with slow heavyweight timetravel mechanisms.