Due to the bug described in SERVER-39074, it is possible for a transaction that uses ignore_prepare=true to perform an update after skipping a prepared update.
When a transaction skips a prepared update, and that prepared update then commits, the transaction performing the conflicting update should get a WT_ROLLBACK.
- depends on
-
SERVER-40176 Cursor seekExact should not use WT_CURSOR:search_near to avoid unintentional prepare conflicts
- Closed
-
SERVER-40177 Enforce prepare conflicts on secondaries
- Closed
-
SERVER-40519 Profiler should do writes with ignore-prepare set to false
- Closed
-
SERVER-41525 Use ignore_prepare=force for transactions that correctly do writes while ignoring prepare conflicts
- Closed
-
WT-4804 Add support for ignore_prepare=force
- Closed
- is related to
-
SERVER-39074 Update outside transaction erasing update from committed prepared transaction
- Closed