Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-26800

mysql.plugin violates plugin_type_initialization_order

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6
    • 10.5, 10.6
    • Plugins
    • None

    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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26795 InnoDB writes error messages about compressed tables upon startup

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              serg Sergei Golubchik
              serg Sergei Golubchik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.