mirror of
https://github.com/MariaDB/server.git
synced 2025-07-29 05:21:33 +03:00
MDEV-30544 Deprecate innodb_defragment and related parameters
There is a little used option innodb_defragment that would make
OPTIMIZE TABLE not rebuild the table as usual for InnoDB, but
instead cause the index B-trees to be optimized in place.
This option uses excessive locking (exclusively locking index trees).
It never covered SPATIAL INDEX or FULLTEXT INDEX. Storage space
was never reclaimed.
Because this option is not particularly useful and causes a
maintenance burden (most recently in
commit de4030e4d4
),
it is best to deprecate it, to prepare for its removal.
This commit is contained in:
@ -279,10 +279,14 @@ SET GLOBAL innodb_limit_optimistic_insert_debug = @old_limit;
|
||||
ALTER TABLE t1 ADD COLUMN b INT, ALGORITHM=INSTANT;
|
||||
SET @old_defragment = @@innodb_defragment;
|
||||
SET GLOBAL innodb_defragment = 1;
|
||||
Warnings:
|
||||
Warning 1287 '@@innodb_defragment' is deprecated and will be removed in a future release
|
||||
OPTIMIZE TABLE t1;
|
||||
Table Op Msg_type Msg_text
|
||||
test.t1 optimize status OK
|
||||
SET GLOBAL innodb_defragment = @old_defragment;
|
||||
Warnings:
|
||||
Warning 1287 '@@innodb_defragment' is deprecated and will be removed in a future release
|
||||
ALTER TABLE t1 ADD vb INT AS (b) VIRTUAL;
|
||||
CHECK TABLE t1;
|
||||
Table Op Msg_type Msg_text
|
||||
|
Reference in New Issue
Block a user