[MDEV-30544] Deprecate innodb_defragment and related parameters Created: 2023-02-02  Updated: 2023-02-21  Resolved: 2023-02-02

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 11.0.1

Type: Task Priority: Blocker
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-30545 Remove innodb_defragment and related ... Closed
Relates
relates to MDEV-5834 Merge Kakao Defragmentation implement... Closed
relates to MDEV-18385 Document use cases and locking behavi... Open
relates to MDEV-28558 The MTR based test innodb_defrag_conc... Closed

 Description   

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 (last, in MDEV-30400 when the B-tree cursors were refactored), I think that it is best to deprecate it, to give advance notice of its future removal.

The following parameters will be deprecated:

  • innodb_defragment
  • innodb_defragment_n_pages
  • innodb_defragment_stats_accuracy
  • innodb_defragment_fill_factor_n_recs
  • innodb_defragment_fill_factor
  • innodb_defragment_frequency

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