Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Replication
-
1
Description
I believe this is only used when eMRC=off. So we should be able to remove that from the storage engine API's surface area as well as the underlying call into WT.
Attachments
Issue Links
- has to be done before
-
WT-9172
remove force configuration for WT_CONNECTION.set_timestamp API
-
- Blocked
-