-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Transactions
-
StorEng - Refinement Pipeline
This came out of investigating WT-10576. Imagine the following scenario:
A table has a transaction open, but prepare has been called on the updates. There aren't any cursors open on the table anymore. So, sweep could potentially come in and close the table as the prepared updates could be evicted to the disk.
What happens when commit/rollback gets called - do we successfully open the table back when resolving the prepared updates?
What if the table gets dropped in the meanwhile - is that allowed?
We should write a test to define the expected behaviour.
Changes from WT-10576 will probably prevent the table from being closed and/or dropped while there is an open transaction - but worth investigating the prepared transactions separate to that ticket.
- is related to
-
WT-10576 Return EBUSY on forced drop if there is an active transaction
- Closed