[MDEV-5839] TokuDB tables not properly cleaned on DROP DATABASE Created: 2014-03-12 Updated: 2014-03-26 Resolved: 2014-03-26 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.0.9 |
| Fix Version/s: | 10.0.10 |
| Type: | Bug | Priority: | Major |
| Reporter: | jocelyn fournier | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Hi, When a database is dropped with Tokudb tables in it, the tables are not properly dropped.
My.cnf :
Thanks and regards, |
| Comments |
| Comment by Sergei Golubchik [ 2014-03-23 ] |
|
Tested in 5.5 tree (with TokuDB 7.1.5) — no bug. So, either it's because of the old TokuDB version in 10.0, and will go away after the next merge (which will happen before 10.0.10 release). Or it may be due to new discovery code in 10.0. Either way, I need to retest after the merge. |
| Comment by jocelyn fournier [ 2014-03-23 ] |
|
Hi Sergei, About the remaining .tokudb file in the FS, can I safely remove them ? Thanks, |
| Comment by Sergei Golubchik [ 2014-03-26 ] |
|
The reason for this bug — DROP DATABASE didn't correctly discover all tables in the database, it only looked at .frm files. As a workaround, if you add SELECT * FROM t1 (or any other statement that uses the table) between CREATE TABLE and DROP DATABASE, then the table will be properly removed. |