Checkpoint cursors are known to be broken in durable history since they no longer represent a snapshot as of a particular time. Also, the cells now contain time pairs that influence visibility.
We should decide whether we can support reading directly from a checkpoint. If not, we should retire that functionality in the API and remove any associated testing. We've disabled some testing of checkpoint cursors in the wt4333_handle_locks test (just grep for FIXME) so we should either remove or re-enable this testing as part of this ticket.
haseeb.bokhari understands the problems involved with supporting checkpoint cursors so he is a good person to talk to before getting started with this work.
- causes
-
WT-9067 test_checkpoint23 assert failure
- Closed
-
WT-9103 MemorySanitizer uninitialised value in __wt_txn_init_checkpoint_cursor
- Closed
-
WT-9104 Assertion fired in test_checkpoint_4_mixed_timestamps and test_checkpoint1[0,1]
- Closed
- is depended on by
-
SERVER-68689 Switch background validation to use checkpoint cursors again
- Closed
-
SERVER-65974 Replace HistoricalIdentTracker with checkpoint cursors
- Closed
- is duplicated by
-
WT-9103 MemorySanitizer uninitialised value in __wt_txn_init_checkpoint_cursor
- Closed
-
WT-9104 Assertion fired in test_checkpoint_4_mixed_timestamps and test_checkpoint1[0,1]
- Closed