The read barrier in question here was added to pair with a WRITE_BARRIER in __rec_append_orig value which was converting an upd->type from WT_UPDATE_BIRTHMARK to WT_UPDATE_STANDARD. A holdover from the lookaside days.
We never change upd->type in the current version of the code an thus a read barrier here isn't required.
Original ticket: WT-5376
- is related to
-
WT-5376 WT_UPDATE.type field can race with visibility checks when returning key/value pairs
-
- Closed
-