You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/guides/57-data-management/04-data-recycle.md
+9-5Lines changed: 9 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -21,12 +21,16 @@ Before DELETE: After DELETE: After VACUUM:
21
21
22
22
## Types of Data to Clean
23
23
24
-
In Databend, there are four main types of data that may need cleaning:
24
+
Databend provides specific commands to clean different types of data. The following table summarizes the data types and their corresponding cleanup commands:
25
25
26
-
1.**Dropped Table Data**: Data files from tables that have been dropped using the DROP TABLE command
27
-
2.**Table History Data**: Historical versions of tables, including snapshots created through UPDATE, DELETE, and other operations
28
-
3.**Orphan Files**: Snapshots, segments, and blocks that are no longer associated with any table
29
-
4.**Spill Temporary Files**: Temporary files created when memory usage exceeds available limits during query execution (for joins, aggregates, sorts, etc.). Databend automatically cleans up these files when queries complete normally. Manual cleanup is only needed in rare cases when Databend crashes or shuts down unexpectedly during query execution.
26
+
| Data Type | Description | Cleanup Command |
27
+
|-----------|-------------|-----------------|
28
+
|**Dropped Table Data**| Data files from tables that have been dropped using the DROP TABLE command |`VACUUM DROP TABLE`|
29
+
|**Table History Data**| Historical versions of tables, including snapshots created through UPDATE, DELETE, and other operations |`VACUUM TABLE`|
30
+
|**Orphan Files**| Snapshots, segments, and blocks that are no longer associated with any table |`VACUUM TABLE`|
31
+
|**Spill Temporary Files**| Temporary files created when memory usage exceeds available limits during query execution (for joins, aggregates, sorts, etc.) |`VACUUM TEMPORARY FILES`|
32
+
33
+
> **Note**: Spill temporary files are typically cleaned automatically by Databend. Manual cleanup is only needed when Databend crashes or shuts down unexpectedly during query execution.
0 commit comments