Timeline for Procedure to recreate table automatically to free InnoDB space
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4, 2019 at 16:45 | vote | accept | Alan | ||
| Nov 2, 2019 at 1:06 | answer | added | Rick James | timeline score: 1 | |
| Nov 2, 2019 at 1:01 | comment | added | Rick James |
And what is the setting of innodb_file_per_table? Please provide SHOW TABLE STATUS LIKE '...'
|
|
| Nov 2, 2019 at 1:00 | comment | added | Rick James |
How big is payload? If each of your 6 rows has a 3GB payload, then 18GB is the real size!
|
|
| Oct 31, 2019 at 17:19 | comment | added | Jesus Uzcanga | Great answers. Did you try TRUNCATE TABLE end then OPTIMIZE TABLE? Doing so, you won't need to drop and create it again. TRUNCATE TABLE is a DDL statement used to delete all rows in a table. DELETE * FROM is a DML statement and does not affect physical files. | |
| Oct 30, 2019 at 23:27 | comment | added | Alan |
Great questions. innodb_file_per_table is enabled, so I am seeing the tablesize in the data directory. I am using 8.0.13 MySQL Community Server right now on Ubuntu 16.04
|
|
| Oct 30, 2019 at 20:07 | comment | added | Jesus Uzcanga | Three questions: 1.- How are you measuring the table sizes? 2.- is the innodb_file_per_table variable enabled?. 3.- MySQL and OS version | |
| Oct 30, 2019 at 20:01 | history | asked | Alan | CC BY-SA 4.0 |