2 ms·
I admit I just skimmed this. But, realistically speaking, what are the DR benefits over just plain out-of-the-box Postgres PITR?
by hn_throwaway_99 4y ago
I admit I just skimmed this. But, realistically speaking, what are the DR benefits over just plain out-of-the-box Postgres PITR?
- fulafel 4y agoThe 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.
- mattashii 4y agoPrimarily, the time-to-recovery to an arbitrary point in time is much lower than when you use vanilla solutions, because Neon doesn't need to recover from a previous checkpoint (potentially hours of WAL), nor does it need a file system / data directory snapshot from around the recovery point. pg_rewind can only do so much, and snapshots require planning ahead for the need for recovery.