Timeline for How to optimize a delete query with a subselect? [closed]
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 20, 2019 at 5:22 | vote | accept | stefgosselin | ||
| Jan 14, 2019 at 20:56 | history | closed |
Hannah Vernon♦ mustaccio LowlyDBA - John M Mr.Brownstone Evan Carroll |
Needs more focus | |
| Jan 12, 2019 at 2:06 | comment | added | Rick James | Here are multiple techniques to deal with big deletes. Deleting more than a thousand rows at a time is costly because of the undo log. | |
| Jan 11, 2019 at 9:33 | comment | added | McNets | You better move 3 million rows into a new table and delete the old one. | |
| Jan 11, 2019 at 4:18 | answer | added | Akina | timeline score: 1 | |
| Jan 11, 2019 at 0:46 | comment | added | danblack | If you are doing these frequently or need to consider resource usage, consider partitioning by the date and dropping a partition. | |
| Jan 11, 2019 at 0:44 | comment | added | danblack |
You'll probably need a larger innodb_log_file_size - see dev.mysql.com/doc/refman/5.7/en/innodb-redo-log.html. A large innodb_buffer_size is also recommended.
|
|
| Jan 11, 2019 at 0:12 | history | edited | Michael Green | CC BY-SA 4.0 |
some line breaks to avoid right-scrolling
|
| Jan 10, 2019 at 21:10 | review | Close votes | |||
| Jan 14, 2019 at 21:00 | |||||
| Jan 10, 2019 at 20:50 | comment | added | Hannah Vernon♦ | I'm voting to close this question as off-topic because it lacks sufficient detail required to facilitate a comprehensive answer. Please see dba.meta.stackexchange.com/questions/2990/… for more details. Add the required details, and we'll likely re-open the question. | |
| Jan 10, 2019 at 20:16 | comment | added | mustaccio | Please take a look at this advice | |
| Jan 10, 2019 at 19:45 | review | First posts | |||
| Jan 10, 2019 at 20:16 | |||||
| Jan 10, 2019 at 19:42 | history | asked | stefgosselin | CC BY-SA 4.0 |