Currently, in snapshot isolation, format worker threads check that repeatable reads work and they get correct data with respect to earlier reads in the transaction immediately before transaction commit/abort.
With timestamps, threads should be able to confirm data associated with a particular timestamp can be read even after the transaction has been committed/aborted, until the timestamp times out of the system.
Extend format to check timestamp reads after transaction commit/abort.
- causes
-
WT-4887 Skip read timestamp required assert during recovery
- Closed
-
WT-4888 Remove support for Berkeley DB
- Closed
-
WT-4890 Improperly configured Jenkins test
- Closed
- is depended on by
-
WT-5188 Assert hit with birthmarks present in __wt_las_insert_block on v4.0 branch
- Closed
-
WT-4612 Improve test coverage for prepare updates older than the oldest
- Closed
- is duplicated by
-
WT-4777 Invalid argument error while committing a timestamp transaction
- Closed
- is related to
-
WT-4738 Tighten rules around use of timestamps
- Closed
- related to
-
WT-5201 Migrate develop test format to mongodb-4.0 branch
- Closed