Bug #29349 | dropping MEMORY table very slow | ||
---|---|---|---|
Submitted: | 26 Jun 2007 1:01 | Modified: | 27 Jun 2007 15:33 |
Reporter: | Jacek Becla | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Memory storage engine | Severity: | S3 (Non-critical) |
Version: | 5.0.27 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | delete, Drop, memory storage, slow, truncate |
[26 Jun 2007 1:01]
Jacek Becla
[26 Jun 2007 10:46]
MySQL Verification Team
regarding the read_buffer_size allocations, I had already filed bug #29178 to discuss that
[2 Feb 2014 14:12]
MySQL Verification Team
this is still a problem. I had around 18GB of memory tables and it took long enough to drop. mysql> drop database test;create database test;use test; Query OK, 126 rows affected (2 min 54.31 sec)