-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
ALL
-
Repl 2019-04-22, Repl 2019-05-06, Repl 2019-05-20, Repl 2019-06-03
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
After SERVER-38906, transactions with local or majority readConcern no longer read at a timestamp. This means that we will not check their read timestamp against the collection's minimum visible snapshot here, so we allow these transactions to read from collections that were created after the transaction was opened. This is illegal in the storage engine. Instead we should record what the most recent visible timestamp is before the transaction, and then use that to check the min visible time when reading a collection.
- is related to
-
-
- Closed
-
-
SERVER-38906 Multi-document transactions should not perform timestamped read ahead of all-committed
-
- Closed
-
- related to
-
-
- Closed
-