Currently, when we are updating the pinned timestamp, we are not considering the checkpoint timestamp. We consider the checkpoint timestamp only when we check the global visibility. This is because we want to the pinned content to be as small as possible in memory before durable history. Now with durable history, there is no need to do that. We can directly consider checkpoint timestamp when we updating the pinned timestamp.
- Does this affect any team outside of WT?
- How likely is it that this use case or problem will occur?
- If the problem does occur, what are the consequences and how severe are they?
Acceptance Criteria (Definition of Done)
Pass mongodb patch build and stress test.
Use existing testing