Timeline for Why MySQL Database is Bigger After Dump/Import?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 10, 2019 at 20:33 | history | edited | RolandoMySQLDBA |
Added backup tag since mysqldump performs backups
|
|
| Sep 30, 2016 at 10:48 | history | tweeted | twitter.com/StackDBAs/status/781807898171215872 | ||
| Sep 13, 2016 at 4:20 | comment | added | Kenaz Chan | Hey thanks for prompt respond. However, I've accepted RonaldoMySQLDBA's answer. After I downgraded MySQL to v5.6, the DB import size is back to normal. | |
| Sep 12, 2016 at 11:39 | vote | accept | Kenaz Chan | ||
| Sep 12, 2016 at 2:54 | comment | added | Rick James |
Can you provide SHOW CREATE TABLE wp_wfLeechers; before and after? Also SHOW TABLE STATUS LIKE 'wp_wfLeechers';
|
|
| Sep 12, 2016 at 2:53 | comment | added | Rick James |
How many tables? Are any of them PARTITIONed? Many columns CHAR as opposed to VARCHAR?
|
|
| Sep 12, 2016 at 2:16 | comment | added | Kenaz Chan | Majority of them are InnoDB, there are some MyISAM though, but not a lot compare to the total number of tables. | |
| Sep 11, 2016 at 3:54 | answer | added | Rick James | timeline score: 0 | |
| Sep 11, 2016 at 3:53 | comment | added | Rick James | What Engine were the tables?? MyISAM? InnoDB? | |
| Sep 9, 2016 at 12:09 | answer | added | RolandoMySQLDBA | timeline score: 2 | |
| Sep 9, 2016 at 10:50 | review | First posts | |||
| Sep 9, 2016 at 12:41 | |||||
| Sep 9, 2016 at 10:46 | history | asked | Kenaz Chan | CC BY-SA 3.0 |