Ensure that table is truly dropped when using DROP TABLE (MDEV-11412)

[MDEV-22826] Presence of Spider prevents tables from being force-deleted from other engines Created: 2020-06-07  Updated: 2020-06-15  Resolved: 2020-06-15

Status: Closed
Project: MariaDB Server
Component/s: Plugins, Server, Storage Engine - Spider
Affects Version/s: N/A
Fix Version/s: N/A

Type: Technical task Priority: Major
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates

 Description   

If Spider engine is loaded into the server (even if it's not used), tables from other engines fail to be force-deleted – DELETE works without errors, but orphan files, e.g. .MYD/.MYI or .ibd, remain on the disk.

--let $datadir= `select @@datadir`
 
 
 
install soname 'ha_spider';
 
 
 
create table t1 (a int);
 
 
 
--remove_file $datadir/test/t1.frm
 
 
 
drop table t1;
 
--echo # Files in <datadir>/test:
 
--list_files $datadir/test

bb-10.5-monty 645f37e49c

 
drop table t1;
 
# Files in datadir/test:
 
db.opt
 
t1.MYD
 
t1.MYI



 Comments   
Comment by Michael Widenius [ 2020-06-09 ]

Fixed in bb-10.5-monty, to be pushed soon..

Comment by Michael Widenius [ 2020-06-15 ]

Corrected code without this issue pushed into 10.5

Generated at Thu Feb 08 09:17:46 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.