-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
13
-
Storage Engines 2020-01-27
Design from the ticket WT-5323 puts a LAS transaction and an application transaction together in a session. These two transactions can be open simultaneously and fail independently of each other. These transaction failures can impact each other and need to be error handled properly. This ticket will address brainstorming the correctness of this transaction interaction for the durable history.
- related to
-
WT-5467 Make history store cursor part of each session, get rid of the cursor pool
- Closed