[MDEV-25800] DROP TABLE unnecessarily accesses .ibd file Created: 2021-05-27  Updated: 2024-01-05

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2, 10.3, 10.4, 10.5, 10.6
Fix Version/s: 10.6

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Debarun Banerjee
Resolution: Unresolved Votes: 2
Labels: performance

Issue Links:
Relates
relates to MDEV-25801 DROP DATABASE very slow after innodb ... Closed
relates to MDEV-21069 Crash on DROP TABLE if the data file ... Closed
relates to MDEV-25773 sysbench-TPCC failed to prepare with ... Closed

 Description   

In stack traces posted to MDEV-25773, we can observe that DROP DATABASE (or DROP TABLE) would end up waiting for the buffer pool mutex, for allocating a page so that the to-be-dropped table could be opened.

This is unnecessary and could cause a crash, in case the data file is corrupted. In MDEV-21069 we already removed writes to the .ibd file on DROP TABLE. There should be no need to read the .ibd file either.
Generated at Thu Feb 08 09:40:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.