mariadb/storage
Thirunarayanan Balathandayuthapani c6de1267dd MDEV-35689 InnoDB system tables cannot be optimized or defragmented
- With the help of MDEV-14795, InnoDB implemented a way to shrink
the InnoDB system tablespace after undo tablespaces have been moved
to separate files (MDEV-29986). There is no way to defragment any
pages of InnoDB system tables. By doing that, shrinking of
system tablespace can be more effective. This patch deals with
defragment of system tables inside ibdata1.

Following steps are done to do the defragmentation of system
tablespace:
1) Make sure that there is no user tables exist in ibdata1

2) Iterate through all extent descriptor pages in system tablespace
and note their states.

3) Find the free earlier extent to replace the lastly used
extents in the system tablespace.

4) Iterate through all indexes of system tablespace and defragment
the tree level by level.

5) Iterate the level from left page to right page and find out
the page comes under the extent to be replaced. If it is then
do step (6) else step(4)

6) Prepare the allocation of new extent by latching necessary
pages. If any error happens then there is no modification of
page happened till step (5).

7) Allocate the new page from the new extent

8) Prepare the associated pages for the block to be modified

9) Prepare the step of freeing of page

10) If any error happens during preparing of associated pages,
freeing of page then restore the page which was modified
during new page allocation

11) Copy the old page content to new page

12) Change the associative pages like left, right and parent page

13) Complete the freeing of old page

Allocation of page from new extent, changing of relative pages,
freeing of page are done by 2 steps. one is prepare which
latches the to be modified pages and checks their validation.
Other is complete(), Do the operation

fseg_validate(): Validate the list exist in inode segment

Defragmentation is enabled only when :autoextend exist in
innodb_data_file_path variable.
2025-04-10 17:13:34 +05:30
..
archive Merge branch '10.11' into 11.0 2024-05-12 12:18:28 +02:00
blackhole Merge 10.11 into 11.4 2024-12-02 11:35:34 +02:00
columnstore ColumnStore 23.10.3-1 2025-01-29 23:57:22 +01:00
connect Merge 10.11 into 11.4 2025-03-28 13:55:21 +02:00
csv Merge 10.11 into 11.4 2024-12-02 11:35:34 +02:00
example Merge 10.11 into 11.4 2025-01-09 07:58:08 +02:00
federated Merge 10.11 into 11.4 2024-12-02 11:35:34 +02:00
federatedx Merge 10.11 into 11.4 2025-03-03 11:07:56 +02:00
heap Fixed costs in JOIN_TAB::estimate_scan_time() and HEAP 2025-02-10 15:59:28 +02:00
innobase MDEV-35689 InnoDB system tables cannot be optimized or defragmented 2025-04-10 17:13:34 +05:30
maria Merge 10.11 into 11.4 2025-03-28 13:55:21 +02:00
mroonga Merge 10.11 into 11.4 2025-01-09 07:58:08 +02:00
myisam Merge 10.11 into 11.4 2025-03-28 13:55:21 +02:00
myisammrg Merge 10.11 into 11.4 2025-01-09 07:58:08 +02:00
oqgraph Merge 10.11 into 11.4 2024-12-02 11:35:34 +02:00
perfschema Merge branch '10.11' into 11.4 2025-01-14 23:45:41 +01:00
rocksdb MDEV-35773 fix test results 2025-01-15 09:49:33 +01:00
sequence Merge branch '10.11' into 11.1 2024-07-08 22:40:16 +02:00
sphinx Merge 10.11 into 11.4 2024-12-02 11:35:34 +02:00
spider Merge 10.11 into 11.4 2025-04-02 10:15:08 +03:00
test_sql_discovery Merge 10.5 into 10.6 2024-06-24 13:09:47 +03:00