Will dropping a large log table quickly free up space in storage?

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: drop大的日志表,存储上面会很快释放空间吗?

| username: TiDBer_Y2d2kiJh

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version] v5.4.0 3tidb 3pd 3tikv
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]
Planning to drop a large log table with approximately 200 million records. I would like to know the principle of the drop operation. After dropping, will the storage space be released quickly?

| username: TIDB-Learner | Original post link

Excerpt from the official documentation:
In TiDB, using `DELETE`, `TRUNCATE`, and `DROP` statements to delete data will not immediately release space. For `TRUNCATE` and `DROP` operations, after reaching TiDB's GC (garbage collection) time (default 10 minutes), TiDB's GC mechanism will delete the data and release the space. For `DELETE` operations, TiDB's GC mechanism will delete the data but will not immediately release the space; instead, the space will be released during subsequent compaction.