Hot answers tagged mysqldump
Please note this Pictorial Representation of ibdata1 (from Vadim Tkachenko) You have many moving parts inside ibdata1 Data Dictionary Double Write Buffer Insert Buffer Rollback Segments Undo Space Almost 3 years ago, I wrote a post addressing why ibdata1 can grow too fast : How can Innodb ibdata1 file grows by 5X even with innodb_file_per_table set? ...
Un-panic. Your queue had lots of rows inserted and quickly deleted, correct? And now it has very few rows in it? Specifically, about 17K? More importantly, there was, at one point, maybe a million rows? So the tablespace expanded to handle it, but has not shrunken. The dump dumped only the data for the current 17K rows. The reload loaded only those ...
OPTIMIZE is probably better because what it does is CREATE TABLE ... Copy all the existing rows over RENAME ... (Some time during or after step 2, the indexes are rebuilt.) Dump and reload: Read the entire table, write to disk DROP TABLE or TRUNCATE TABLE and CREATE TABLE ... Read the dump, inserting into the table This is slower because of the ...
16777216 is a reasonable value; 1024 is not. The error message is just a warning, saying that 1024 is below the minimum allowed value. Try the mysqldump with 16777216.
Only top voted, non community-wiki answers of a minimum length are eligible