Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5(EOL), 10.6, 10.11, 11.4, 11.8, 12.3
-
None
-
Not for Release Notes
Description
Plugins are expected to be initialized in the order specified by plugin_type_initialization_order.
With one exception of the engine of mysql.plugin table (usually MyISAM), it should go first.
But in fact, first all built-in plugins and command-line plugins are initialized in the plugin_type_initialization_order. After that all mysql.plugin are initialized in the plugin_type_initialization_order.
As a result, encryption and compression plugins from mysql.plugin are initialized after built-in InnoDB.
Attachments
Issue Links
- causes
-
MDEV-26795 InnoDB writes error messages about compressed tables upon startup
-
- Closed
-
- relates to
-
MDEV-36147 MariaDB cannot open page-compressed InnoDB tables at startup if innodb_compression_algorithm other than zlib is specified
-
- In Review
-