13 Oct
2014
13 Oct
'14
4:53 p.m.
Hi, Andrew! On Sep 17, Andrew Braithwaite wrote:
It only seems to happen when replicating DROP TABLE IF NOT EXISTS from a master, not when running it directly on that server.
I can replicate this problem every time.
I tried to repeat it (just like you said, create a master-slave setup, DROP TABLE IF EXISTS on master, see what happens on the slave). Everything worked as documented - both .frm and .ibd files were deleted. Could you try to create a complete repeatable test case? Also - as it looks like a bug - you could consider reporting it at mariadb.org/jira
After dropping tables on my MariaDB 10.0.13 database server, the .frm files are removed but the .ibd files remain behind. Has anyone seen this before?
Regards, Sergei