As part of WT-6257, we noticed that we're passing true as the exclusive argument to wt_row_modify. This assumes exclusive access to the page and skips locking when adding to an insert list.
In the case of history store writes, this is definitely not true so we should use false instead. It's not clear whether this fixes WT-6257. We're in the process of figuring that out.
- is duplicated by
-
WT-6291 __split_insert: SEGV on unknown address caused by a READ memory access
- Closed