It's common for a user to want to read at some time >= T. In those cases, using `round_to_oldest=true` is attractive. However, it's not possible to always know what read timestamp is used.
AFAIK, the field is easily accessible on a WT_SESSION_IMPL's transaction structure, it would be nice to expose it with some API.
- is depended on by
-
SERVER-35821 readConcern:snapshot transactions need a read timestamp <= WT's all_committed point
-
- Closed
-
- links to