Timeline for Why is DROP DATABASE taking so long? (MySQL)
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2023 at 13:28 | comment | added | baptx | Even after killing the process, if we try to drop the database again, it still takes forever. The processlist command displays the state "closing tables". When I waited until the drop database command finished, it said "ERROR 2013 (HY000): Lost connection to MySQL server during query" and did not drop the database. I got this issue since I shutdown my computer but if was hanging because of MySQL (MariaDB) so I had to force shutdown. | |
| Jan 4, 2019 at 10:05 | comment | added | Stefan Magnuson |
@BugsBuggy A common way in which this can occur is if another process (e.g. a web server, or in this case an import process) is running and is connected to the database. When you issue the DROP DATABASE command the server will not proceed until all connections have been closed.
|
|
| Jul 26, 2018 at 5:31 | history | edited | Paul White♦ | CC BY-SA 4.0 |
Removed obsolete accepted answer remark, incorporated comment information
|
| Apr 2, 2013 at 23:17 | vote | accept | Buttle Butkus | ||
| S Mar 27, 2013 at 5:49 | review | Late answers | |||
| Mar 27, 2013 at 9:43 | |||||
| S Mar 27, 2013 at 5:49 | review | First posts | |||
| Mar 27, 2013 at 6:25 | |||||
| Mar 27, 2013 at 5:32 | history | answered | Stefan Magnuson | CC BY-SA 3.0 |