Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
The InnoDB system tablespace is an opaque entity that contains essential system data, such as the transaction system state (undo logs could also be in separate tablespaces) and part of the data dictionary information.
Tablespaces cannot shrink in InnoDB, and the system tablespace cannot be reinitialized. If the system tablespace grows (for example, someone accidentally creates a huge table in it, or accidentally forgets to commit a transaction, causing undo logs to grow, or the change buffer grows for some reason), there is no other remedy than importing or loading the data to a newly initialized innoDB instance.
Similarly, if the system tablespace gets corrupted, it is ‘game over’.
This is an umbrella task consisting of subtasks to replace the various system objects stored in the InnoDB system tablespace. The actual work will be done in the subtasks.
Attachments
Issue Links
- is blocked by
-
MDEV-11657 Cross-engine transaction metadata
- Open
-
MDEV-11658 Simpler, faster IMPORT of InnoDB tables
- Open
-
MDEV-11659 Move the InnoDB doublewrite buffer to flat files
- Open
-
MDEV-15020 Server hangs due to InnoDB persistent statistics or innodb_stats_auto_recalc
- Closed
-
MDEV-17567 Atomic DDL
- Closed
-
MDEV-19506 Remove the global sequence DICT_HDR_ROW_ID for DB_ROW_ID
- Closed
-
MDEV-21463 Support FULLTEXT INDEX for all storage engines
- Open
-
MDEV-22343 Remove SYS_TABLESPACES and SYS_DATAFILES
- Closed
-
MDEV-28730 Remove internal parser usage from InnoDB fts
- Open
-
MDEV-29985 Remove the parameter innodb_file_per_table
- Stalled
- relates to
-
MDEV-15185 PARTITION files removed, but not from INFORMATION_SCHEMA.INNODB_SYS_TABLES
- Closed
-
MDEV-21867 Unsafe writes in fil_write_flushed_lsn()
- Closed