A sudden disk‑usage alarm reveals MySQL’s ibtmp1 temporary tablespace ballooning to 192 GB, and the article walks through why it happens, how to safely clear it, set size limits, and pinpoint the inefficient SQL that caused the explosion.
This article walks through a real‑world case where a MySQL instance showed an abnormal 13 GB data_free value, explains how the ibtmp1 temporary tablespace caused the growth, demonstrates verification steps with sysbench and SQL queries, and provides configuration and operational solutions to prevent and resolve the issue.
This article details a real‑world case where an RDS MySQL instance ran out of disk space due to an oversized temporary tablespace, explains the root‑cause analysis of a massive Cartesian‑product query, and provides step‑by‑step remediation and preventive measures for both MySQL 5.7 and 8.0.
This article analyzes how MySQL's temporary tablespace (ibtmp1) grows when using JDBC with the useCursorFetch=true parameter, why errors are hidden, presents test scenarios reproducing the issue, compares segment and stream reading methods, and proposes configuration and code‑level solutions to control temporary space and ensure proper error reporting.
This article explains the new shared temporary tablespace introduced in MySQL 5.7, how to configure its size and location with innodb_temp_data_file_path, compares it with tmpdir, demonstrates the impact on compressed and uncompressed InnoDB temporary tables, and highlights related parameters and potential pitfalls.
