|
I'm not sure if this will be useful. It sounds like this check boils down to "ensure that dblocks work", which is an odd thing to check in this particular area of the code.
Note that in order for oplog visibility wait to actually block, there needs to be an oplog hole. For there to be an oplog hole, there needs to be an in-progress transaction. For there to be an in-progress transaction, a dblock must be held by that transaction. For a dblock to be held by that transaction, it is impossible for another thread to hold an incompatible dblock and also be in the oplog visibility wait call. QED.
|