-
Type: New Feature
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
8
-
2023-04-18 Leviosa Not Leviosa, 2023-05-02 StorEng Bug Bash
The goal of this configuration would be to relax restrictions that are enforced because tables may generate historical versions. Specifically, this restriction for truncate. Insert-only tables don't generate historical data; in principle, this should allow for fast-truncating non-logged tables which do not use a timestamp.
Note that MongoDB plans to fast-truncate these tables on each mongod in a replica set, regardless of the mongod's replication states; this requires using no_timestamp.
- is related to
-
WT-10949 Allow truncate operation with no timestamp for non standalone builds
- Closed
- related to
-
SERVER-74749 Integrate Truncate Markers with Change Collection remover
- Closed
-
SERVER-75005 Integrate pre-image collection removal with new truncate mechanism
- Closed