mirror of https://gitee.com/bigwinds/arangodb
6d107beeda
* don't run compact() on a collection after a truncate() was done in the same transaction running compact() in the same transaction will only increase the data size on disk due to RocksDB not being able to remove any documents physically due to the snapshot we take at transaction start. Decoupling the truncate transaction from the compact operation allows finishing the truncate transaction first, so we can get rid of the snapshot. Running compact afterwards is then free to physically remove all the data. As a nice side effect this change will also speed up the truncation of larger collections, because the compact will run faster. This change also exposes db.<collection>.compact() in the arangosh, in order to manually run a compaction on the data range of a collection should it be needed for maintenance. * fix documentation anchors |
||
|---|---|---|
| .. | ||
| EngineSelectorFeature.cpp | ||
| EngineSelectorFeature.h | ||
| PhysicalCollection.cpp | ||
| PhysicalCollection.h | ||
| StorageEngine.h | ||
| StorageEngineFeature.h | ||
| TransactionCollection.cpp | ||
| TransactionCollection.h | ||
| TransactionState.cpp | ||
| TransactionState.h | ||
| WalAccess.cpp | ||
| WalAccess.h | ||