Documentation Home
MySQL 8.0 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 34.7Mb
PDF (A4) - 34.7Mb
PDF (RPM) - 32.6Mb
HTML Download (TGZ) - 8.2Mb
HTML Download (Zip) - 8.3Mb
HTML Download (RPM) - 7.1Mb
Man Pages (TGZ) - 129.9Kb
Man Pages (Zip) - 185.4Kb
Info (Gzip) - 3.2Mb
Info (Zip) - 3.2Mb

MySQL 8.0 Reference Manual  /  MySQL Server Administration  /  MySQL Server Components

Pre-General Availability Draft: 2018-01-12

5.5 MySQL Server Components

MySQL Server includes a component-based infrastructure for extending server capabilities:

  • A component provides services that are available to the server and other components. (With respect to service use, the server is a component, equal to other components.) Components interact with each other only through the services they provide.

  • The INSTALL COMPONENT and UNINSTALL COMPONENT SQL statements enable component loading and unloading.

  • A loader service handles component loading and unloading, and also lists loaded components in the mysql.component system table that serves as a registry.

The SQL statements for component manipulation affect server operation and the mysql.component system table as follows:

  • INSTALL COMPONENT loads components into the server. The components become active immediately. The loader service also registers loaded components in the mysql.component system table. For subsequent server restarts, any components listed in mysql.component are loaded by the loader service during the startup sequence. This occurs even if the server is started with the --skip-grant-tables option.

  • UNINSTALL COMPONENT deactivates components and unloads them from the server. The loader service also unregisters the components from the mysql.component system table so that they are no longer loaded during the startup sequence for subsequent server restarts.

To see which components are installed, use this statement:

SELECT * FROM mysql.component;

MySQL distributions include several components that implement server extensions:

System variables implemented by a server component are exposed when the component is installed and have names that begin with a component-specific prefix. For example, the log_filter_dragnet error log filter component implements a system variable named log_error_filter_rules, the full name of which is dragnet.log_error_filter_rules. To refer to this variable, use the full name.

For information about the internal implementation of components, see For example, if you intend to write your own components, this information is important for understanding how components work.

User Comments
Sign Up Login You must be logged in to post a comment.