-
Type:
Task
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: Documentation, Locking, Storage Engine - InnoDB
-
Labels:
Using MariaDB 10.3, I've just tested the Defragmentation for the first time.
I added to my.cnf:
innodb_defragment = 1
.
And then, after restart, I tried "OPTIMIZE TABLE xxxx" on a frequently used table (lots of INSERTs per second), to see how it goes.
I see that pretty much every INSERT query was getting stuck waiting for locks to be released.
.
This doesn't seem to be an improvement over the original OPTIMIZE which creates a new temp table and then swaps, and consequently the table file will be much shorter.
While the new OPTIMIZE using defragmentation locks the table and the file won't get shorter.
.
.
Is it intentional that OPTIMIZE using defragmentation locks the table?
MDEV-9155 is marked as Fixed/Closed since April 2017, so I assumed this would not lock anymore.
.
Thanks!
- relates to
-
MDEV-11336 Enable defragmentation on 10.2 when tests pass
-
- Closed
-