Investigate the possibility of using this parameter to deactivate storing timestamps past the lastAppliedOpTime. That is, if this parameter was disabled, then instead of setting oldest_timestamp at the commit level, we would set it based on the lastAppliedOpTime.
- depends on
-
WT-3762 Allow the oldest_timestamp to be moved backwards.
- Closed
- related to
-
SERVER-31350 make enableMajorityReadConcern parameter a no-op
- Closed
-
SERVER-36982 Reintroduce enableMajorityReadConcern:false server parameter
- Closed