Rechercher dans le manuel MySQL

27.2 Using the sys Schema

You can make the sys schema the default schema so that references to its objects need not be qualified with the schema name:

  1. mysql> USE sys;
  2. Database changed
  3. mysql> SELECT * FROM version;
  4. +-------------+---------------+
  5. | sys_version | mysql_version |
  6. +-------------+---------------+
  7. | 2.0.0       | 8.0.13-debug  |
  8. +-------------+---------------+

(The version view shows the sys schema and MySQL server versions.)

To access sys schema objects while a different schema is the default (or simply to be explicit), qualify object references with the schema name:

  1. mysql> SELECT * FROM sys.version;
  2. +-------------+---------------+
  3. | sys_version | mysql_version |
  4. +-------------+---------------+
  5. | 2.0.0       | 8.0.13-debug  |
  6. +-------------+---------------+

The sys schema contains many views that summarize Performance Schema tables in various ways. Most of these views come in pairs, such that one member of the pair has the same name as the other member, plus a x$ prefix. For example, the host_summary_by_file_io view summarizes file I/O grouped by host and displays latencies converted from picoseconds to more readable values (with units);

  1. mysql> SELECT * FROM sys.host_summary_by_file_io;
  2. +------------+-------+------------+
  3. | host       | ios   | io_latency |
  4. +------------+-------+------------+
  5. | localhost  | 67570 | 5.38 s     |
  6. | background |  3468 | 4.18 s     |
  7. +------------+-------+------------+

The x$host_summary_by_file_io view summarizes the same data but displays unformatted picosecond latencies:

  1. mysql> SELECT * FROM sys.x$host_summary_by_file_io;
  2. +------------+-------+---------------+
  3. | host       | ios   | io_latency    |
  4. +------------+-------+---------------+
  5. | localhost  | 67574 | 5380678125144 |
  6. | background |  3474 | 4758696829416 |
  7. +------------+-------+---------------+

The view without the x$ prefix is intended to provide output that is more user friendly and easier for humans to read. The view with the x$ prefix that displays the same values in raw form is intended more for use with other tools that perform their own processing on the data. For additional information about the differences between non-x$ and x$ views, see Section 27.4.3, “sys Schema Views”.

To examine sys schema object definitions, use the appropriate SHOW statement or INFORMATION_SCHEMA query. For example, to examine the definitions of the session view and format_bytes() function, use these statements:

  1. mysql> SHOW CREATE VIEW sys.session;
  2. mysql> SHOW CREATE FUNCTION sys.format_bytes;

However, those statements display the definitions in relatively unformatted form. To view object definitions with more readable formatting, access the individual .sql files found under the scripts/sys_schema in MySQL source distributions. Prior to MySQL 8.0.18, the sources are maintained in a separate distribution available from the sys schema development website at https://github.com/mysql/mysql-sys.

Neither mysqldump nor mysqlpump dump the sys schema by default. To generate a dump file, name the sys schema explicitly on the command line using either of these commands:

mysqldump --databases --routines sys > sys_dump.sql
mysqlpump sys > sys_dump.sql

To reinstall the schema from the dump file, use this command:

mysql < sys_dump.sql

Find a PHP function

Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-sys-schema-usage.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:en Manuel MySQL : https://dev.mysql.com/

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut