-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Transactions
-
None
-
Storage Engines - Foundations
-
None
-
None
As part of the PIT reads project, we are shipping the primary's oldest timestamp around as part of checkpoint metadata. This timestamp defines the oldest reachable content in the shared table.
Secondaries should use this timestamp to flag running transactions that are reading at a timestamp older than this, since we can't service their reads after picking up a new checkpoint with an oldest timestamp later than the transaction's read timestamp. These transactions need to be rolled back.
- related to
-
WT-16259 Understand prepared transactions behaviour when failing a transaction due to expired history
-
- Backlog
-