diff options
| author | Ruby Chen <ruby.chen@mongodb.com> | 2023-03-23 05:21:51 +0000 |
|---|---|---|
| committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2023-03-23 05:55:44 +0000 |
| commit | 9e41b3deb1e3400415e7c9c6f50d906ec5c5a19e (patch) | |
| tree | 90cf6cdcf1c6517d2ee46ae5417e62c59b061330 /src/third_party/wiredtiger/src/rollback_to_stable | |
| parent | 48047394eb8b2814458cd300ea2341eb62c58640 (diff) | |
| download | mongo-9e41b3deb1e3400415e7c9c6f50d906ec5c5a19e.tar.gz | |
Import wiredtiger: e691f00b4dc94fb9097c8a5e00c28db887fce45c from branch mongodb-master
ref: b8b81fd663..e691f00b4d
for: 7.0.0-rc0
WT-10273: Add new sections to RTS architecture guide
Diffstat (limited to 'src/third_party/wiredtiger/src/rollback_to_stable')
| -rw-r--r-- | src/third_party/wiredtiger/src/rollback_to_stable/rts_btree.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/src/third_party/wiredtiger/src/rollback_to_stable/rts_btree.c b/src/third_party/wiredtiger/src/rollback_to_stable/rts_btree.c index 1042d7b0c74..3e3257bcbd0 100644 --- a/src/third_party/wiredtiger/src/rollback_to_stable/rts_btree.c +++ b/src/third_party/wiredtiger/src/rollback_to_stable/rts_btree.c @@ -404,10 +404,6 @@ __rts_btree_ondisk_fixup_key(WT_SESSION_IMPL *session, WT_REF *ref, WT_ROW *rip, * after further operations on that same key. Rollback to stable should ignore such records * for timestamp ordering verification. * - * If we have fixed the missing timestamps, then the newer update reinserted with an older - * timestamp may have a durable timestamp that is smaller than the current stop durable - * timestamp. - * * It is possible that there can be an update in the history store with a max stop timestamp * in the middle of the same key updates. This occurs when the checkpoint writes the * committed prepared update and further updates on that key including the history store |