-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Transactions
-
None
-
Storage Engines, Storage Engines - Transactions
-
SE Transactions - 2025-10-10
-
3
We have enabled timestamped truncate for mongodb. Therefore, we can enable the timestamp usage check for fast truncate.
case WT_TXN_OP_REF_DELETE: /* * For non-standalone builds, skip truncate commit timestamp validation, as MongoDB * doesn't use timestamps with truncate operations. */ #ifdef WT_STANDALONE_BUILD WT_ERR(__wt_txn_op_set_timestamp(session, op, true)); #else WT_ERR(__wt_txn_op_set_timestamp(session, op, false)); #endif
- is related to
-
WT-15608 Aggregated timestamp validation can fail with a 0 timestamped page deleted structure
-
- Closed
-
-
WT-15616 dist/s_all pass with failed s_test_suite_no_executable check
-
- Closed
-
-
WT-15626 Fix RTS verbose time window output
-
- Closed
-
-
WT-15622 Skip eviction walk on read only btrees if we are only look for dirty and updates data
-
- Closed
-
-
WT-15595 Ignore eviction target/trigger in follower mode
-
- Closed
-
- related to
-
WT-15041 Handle abandoned checkpoints in PALM
-
- Closed
-
-
WT-15634 failed: s-outdated-fixmes on infrequent-checks [wiredtiger @ fbae136d]
-
- Closed
-