Right now, whenever we open existing history cursors, we don't assume that other threads, can actually write during verification. This can cause inconsistencies, and might cause verification to actually fail. To fix this, everytime we open up a history store cursor we should do a begin_transaction with isolation snapshot. This allows the data not to change while we run verification.
- related to
-
WT-5606 Read a consistent view of the history store when verifying
- Closed