-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Transactions
-
None
-
Storage Engines, Storage Engines - Transactions
-
SE Transactions - 2025-08-29, SE Transactions - 2025-09-12
-
8
Design a data structure to store all the identified prepared transactions and their updates in recovery. The prototype implementation stores the updates in an internal session and uses an array to store the internal sessions with prepared transactions.
This approach limits the number of prepared transactions to the number of sessions we can concurrently open, which is not scalable.
We need to design a data structure to allow us store arbitrary number of prepared transactions in recovery.
A simple idea is to create a structure __wt_prepared_txn to store all the WT_TXN_OP of a prepared transaction without initializing a real session and transaction. Then we can use a hashmap to identify the prepared transaction with its prepared id.
- is related to
-
WT-15299 Precise checkpoint data mismatch
-
- Closed
-
-
WT-15238 Found an update with max stop timestamp when inserting data to the history store
-
- Closed
-
-
WT-15309 Memory leak when allocating multi->block_meta
-
- Closed
-
-
WT-15316 Update nlohmann/json to avoid compilation warnings
-
- Closed
-
- related to
-
WT-15011 Return more specific error message about what caused WT_WRITE_CONFLICT
-
- Closed
-