In WT-7918, we temporarily allow setting the prepare timestamp smaller than or equal to the latest active read timestamp with roundup prepare config for mongodb to fix an urgent bug. However, after we have provided a api to return the last key in a table (WT-7992) and mongodb has switched to this new api (SERVER-58409). We should revert the change we made in WT-7918.
- depends on
-
SERVER-58409 Startup RecordId initialization is flawed with durable history and reconstructing prepared transactions
-
- Closed
-
-
WT-7992 Provide API to return the last key in a table regardless of visibility
-
- Closed
-