For a particular very specific use-case, we have the need to start a transaction and set its read timestamp to a value that could possibly be less-than/earlier-than the oldest timestamp.
The use case is for when an existing open transaction has a read timestamp X, and another transaction is then opened and also set read timestamp to X, prior to the first transaction being closed.
- is depended on by
-
SERVER-51302 Override read timestamp check for refreshTransaction
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-47681 Background validation uses the kNoOverlap read source instead of kAllDurableSnapshot to prevent us from having to take the PBWM lock on secondaries
-
- Closed
-