Details
Description
The weakness of mixed-mode is that it opens the door to forgetting to set a timestamp and creating a data-consistency problem where a reader won’t see correct data. If mixed-mode were limited to specific transactions, it greatly diminishes the chance of that happening in a random code path. We should add a flag to the transaction_begin API that allows a commit timestamp of 0. The write_timestamp_usage configuration basically goes away because there are 2 settings, ordered and never, and if you use timestamps, you’re doing ordered.
Attachments
Issue Links
- has to be done after
-
WT-9055 Remove out-of-order timestamp support
-
- Closed
-
- has to be done before
-
WT-9276
remove support for mixed-mode
-
- Closed
-
- is depended on by
-
SERVER-65971 Avoid/Suppress mixed_mode write on config.transactions
-
- Closed
-
-
-
- Closed
-