mysql show schema_快速入门 · xiaoboluo768/mysql-system-schema Wiki · GitHub
首先，檢查performance_schema是否支持(performance_schema被視為存儲引擎。如果該引擎可用，則應該在INFORMATION_SCHEMA.ENGINES表或SHOW ENGINES語句的輸出中看到它的SUPPORT值為YES)：
qogir_env@localhost : performance_schema 02:41:41> SELECT * FROM INFORMATION_SCHEMA.ENGINES WHERE ENGINE ='PERFORMANCE_SCHEMA';
+--------------------+---------+--------------------+--------------+------+------------+
| ENGINE | SUPPORT | COMMENT | TRANSACTIONS | XA | SAVEPOINTS |
+--------------------+---------+--------------------+--------------+------+------------+
| PERFORMANCE_SCHEMA | YES | Performance Schema | NO | NO | NO |
+--------------------+---------+--------------------+--------------+------+------------+
1 row in set (0.00 sec)
qogir_env@localhost : performance_schema 02:41:54> show engines;
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| Engine | Support | Comment | Transactions | XA | Savepoints |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| CSV | YES | CSV storage engine | NO | NO | NO |
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| MyISAM | YES | MyISAM storage engine | NO | NO | NO |
| BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO |
| InnoDB | DEFAULT | Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
| PERFORMANCE_SCHEMA | YES | Performance Schema | NO | NO | NO |
| ARCHIVE | YES | Archive storage engine | NO | NO | NO |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO |
| FEDERATED | NO | Federated MySQL storage engine | NULL | NULL | NULL |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
9 rows in set (0.00 sec)
啟用performance_schema
performance_schema在5.7.x版本中默認啟用(5.6.x版本默認關閉)，要顯式啟用或關閉時，使用參數perform_schema=ON|OFF設置，并在my.cnf中進行配置
[mysqld]
performance_schema = ON
檢查啟用是否成功，mysqld啟動之后，通過如下語句查看是否啟用成功(值為ON表示performance_schema已初始化成功且可以使用了。如果值為OFF表示在啟用performance_schema時發生某些錯誤。可以查看錯誤日志進行排查)
qogir_env@localhost : performance_schema 03:13:10> SHOW VARIABLES LIKE 'performance_schema';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
| performance_schema | ON |
+--------------------+-------+
1 row in set (0.00 sec)
performance_schema引擎相關的數據存儲在performance_schema數據庫下的相關表中。可以通過從INFORMATION_SCHEMA.tables表和直接在performance_schema庫下使用show tables語句來查看有哪些performance_schema引擎表，以便可以使用show create table語句來查看表結構等信息：
qogir_env@localhost : performance_schema 03:13:22> SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES \
WHERE TABLE_SCHEMA ='performance_schema' and engine='performance_schema';
+------------------------------------------------------+
| TABLE_NAME |
+------------------------------------------------------+
| accounts |
| cond_instances |
......
| users |
| variables_by_thread |
+------------------------------------------------------+
87 rows in set (0.00 sec)
qogir_env@localhost : performance_schema 03:20:43> use performance_schema
Database changed
qogir_env@localhost : performance_schema 03:21:06> show tables from performance_schema;
+------------------------------------------------------+
| Tables_in_performance_schema |
+------------------------------------------------------+
| accounts |
| cond_instances |
......
| users |
| variables_by_thread |
+------------------------------------------------------+
87 rows in set (0.00 sec)
qogir_env@localhost : performance_schema 03:21:09> show create table performance_schema.accounts;
| Table | Create Table
| accounts | CREATE TABLE `accounts` (
`USER` char(32) CHARACTER SET utf8 COLLATE utf8_bin DEFAULT NULL,
`HOST` char(60) CHARACTER SET utf8 COLLATE utf8_bin DEFAULT NULL,
`CURRENT_CONNECTIONS` bigint(20) NOT NULL,
`TOTAL_CONNECTIONS` bigint(20) NOT NULL
) ENGINE=PERFORMANCE_SCHEMA DEFAULT CHARSET=utf8 |
1 row in set (0.00 sec)
performance_schema庫下的表可以按照監視不同的對象進行分組，如下
# 監視語句的相關事件的表(監視器的事件數據還可以根據事件維度和是否經過聚合來分為當前事件表events_statements_current、歷史事件表events_statements_history和events_statements_history_long、聚合后的摘要表*summary*，其中，summary表還可以根據帳號，主機，程序，線程，用戶和全局再進行細分)
qogir_env@localhost : performance_schema 03:51:36> show tables like 'events_statement%';
+----------------------------------------------------+
| Tables_in_performance_schema (%statement%) |
+----------------------------------------------------+
| events_statements_current |
| events_statements_history |
| events_statements_history_long |
| events_statements_summary_by_account_by_event_name |
| events_statements_summary_by_digest |
| events_statements_summary_by_host_by_event_name |
| events_statements_summary_by_program |
| events_statements_summary_by_thread_by_event_name |
| events_statements_summary_by_user_by_event_name |
| events_statements_summary_global_by_event_name |
+----------------------------------------------------+
11 rows in set (0.00 sec)
# 監視等待事件的表
qogir_env@localhost : performance_schema 03:53:51> show tables like 'events_wait%';
+-----------------------------------------------+
| Tables_in_performance_schema (%wait%) |
+-----------------------------------------------+
| events_waits_current |
| events_waits_history |
| events_waits_history_long |
| events_waits_summary_by_account_by_event_name |
| events_waits_summary_by_host_by_event_name |
| events_waits_summary_by_instance |
| events_waits_summary_by_thread_by_event_name |
| events_waits_summary_by_user_by_event_name |
| events_waits_summary_global_by_event_name |
+-----------------------------------------------+
12 rows in set (0.01 sec)
# 監視alter table的階段事件的表
qogir_env@localhost : performance_schema 03:55:07> show tables like 'events_stage%';
+------------------------------------------------+
| Tables_in_performance_schema (%stage%) |
+------------------------------------------------+
| events_stages_current |
| events_stages_history |
| events_stages_history_long |
| events_stages_summary_by_account_by_event_name |
| events_stages_summary_by_host_by_event_name |
| events_stages_summary_by_thread_by_event_name |
| events_stages_summary_by_user_by_event_name |
| events_stages_summary_global_by_event_name |
+------------------------------------------------+
8 rows in set (0.00 sec)
# 監視事務相關的事件的表
qogir_env@localhost : performance_schema 03:55:30> show tables like 'events_transaction%';
+------------------------------------------------------+
| Tables_in_performance_schema (%transaction%) |
+------------------------------------------------------+
| events_transactions_current |
| events_transactions_history |
| events_transactions_history_long |
| events_transactions_summary_by_account_by_event_name |
| events_transactions_summary_by_host_by_event_name |
| events_transactions_summary_by_thread_by_event_name |
| events_transactions_summary_by_user_by_event_name |
| events_transactions_summary_global_by_event_name |
+------------------------------------------------------+
8 rows in set (0.00 sec)
# 監視文件系統層調用的表
qogir_env@localhost : performance_schema 03:58:27> show tables like '%file%';
+---------------------------------------+
| Tables_in_performance_schema (%file%) |
+---------------------------------------+
| file_instances |
| file_summary_by_event_name |
| file_summary_by_instance |
+---------------------------------------+
3 rows in set (0.01 sec)
# 監視內存使用的表
qogir_env@localhost : performance_schema 03:58:38> show tables like '%memory%';
+-----------------------------------------+
| Tables_in_performance_schema (%memory%) |
+-----------------------------------------+
| memory_summary_by_account_by_event_name |
| memory_summary_by_host_by_event_name |
| memory_summary_by_thread_by_event_name |
| memory_summary_by_user_by_event_name |
| memory_summary_global_by_event_name |
+-----------------------------------------+
5 rows in set (0.01 sec)
數據庫剛剛初始化并啟動時，并非所有instruments和consumers都啟用了，所以默認不會收集所有的事件，可能你需要檢測的事件并沒有打開，需要進行設置，可以使用如下兩個語句打開對應的instruments和consumers(行計數可能會因MySQL版本而異)：
qogir_env@localhost : performance_schema 03:34:40> UPDATE setup_instruments SET ENABLED = 'YES', TIMED = 'YES' where name like 'wait%';;
Query OK, 0 rows affected (0.00 sec)
Rows matched: 323 Changed: 0 Warnings: 0
qogir_env@localhost : performance_schema 04:23:40> UPDATE setup_consumers SET ENABLED = 'YES' where name like '%wait%';
Query OK, 3 rows affected (0.04 sec)
Rows matched: 3 Changed: 3 Warnings: 0
要查看server當前正在做什么，可以通過查詢events_waits_current表來得知，該表中每個線程只包含一行數據，用于顯示每個線程的最新監視事件(正在做的事情)：
qogir_env@localhost : performance_schema 04:23:52> SELECT * FROM events_waits_current limit 1\G
*************************** 1. row ***************************
THREAD_ID: 4
EVENT_ID: 60
END_EVENT_ID: 60
EVENT_NAME: wait/synch/mutex/innodb/log_sys_mutex
SOURCE: log0log.cc:1572
TIMER_START: 1582395491787124480
TIMER_END: 1582395491787190144
TIMER_WAIT: 65664
SPINS: NULL
OBJECT_SCHEMA: NULL
OBJECT_NAME: NULL
INDEX_NAME: NULL
OBJECT_TYPE: NULL
OBJECT_INSTANCE_BEGIN: 955681576
NESTING_EVENT_ID: NULL
NESTING_EVENT_TYPE: NULL
OPERATION: lock
NUMBER_OF_BYTES: NULL
FLAGS: NULL
1 row in set (0.02 sec)
# 該事件信息表示線程ID為4的線程正在等待innodb存儲引擎的log_sys_mutex鎖，這是innodb存儲引擎的一個互斥鎖，等待時間為65664皮秒(*_ID列表示事件來自哪個線程、事件編號是多少；EVENT_NAME表示檢測到的具體的內容；SOURCE表示這個檢測代碼在哪個源文件中以及行號；計時器字段TIMER_START、TIMER_END、TIMER_WAIT分別表示該事件的開始時間、結束時間、以及總的花費時間，如果該事件正在運行而沒有結束，那么TIMER_END和TIMER_WAIT的值顯示為NULL。注：計時器統計的值是近似值，并不是完全精確)
_current表中每個線程只保留一條記錄，且一旦線程完成工作，該表中不會再記錄該線程的事件信息，_history表中記錄每個線程已經執行完成的事件信息，但每個線程的只事件信息只記錄10條，再多就會被覆蓋掉，*_history_long表中記錄所有線程的事件信息，但總記錄數量是10000行，超過會被覆蓋掉，咱們查看一下這個表：
qogir_env@localhost : performance_schema 06:14:08> SELECT THREAD_ID,EVENT_ID,EVENT_NAME,TIMER_WAIT FROM events_waits_history ORDER BY THREAD_ID limit 21;
+-----------+----------+------------------------------------------+------------+
| THREAD_ID | EVENT_ID | EVENT_NAME | TIMER_WAIT |
+-----------+----------+------------------------------------------+------------+
| 4 | 341 | wait/synch/mutex/innodb/fil_system_mutex | 84816 |
| 4 | 342 | wait/synch/mutex/innodb/fil_system_mutex | 32832 |
| 4 | 343 | wait/io/file/innodb/innodb_log_file | 544126864 |
| 4 | 344 | wait/synch/mutex/innodb/fil_system_mutex | 55632 |
| 4 | 345 | wait/synch/mutex/innodb/log_sys_mutex | 32832 |
| 4 | 346 | wait/synch/mutex/innodb/fil_system_mutex | 69312 |
| 4 | 347 | wait/synch/mutex/innodb/fil_system_mutex | 23712 |
| 4 | 348 | wait/io/file/innodb/innodb_log_file | 693076224 |
| 4 | 349 | wait/synch/mutex/innodb/fil_system_mutex | 65664 |
| 4 | 350 | wait/synch/mutex/innodb/log_sys_mutex | 25536 |
| 13 | 2260 | wait/synch/mutex/innodb/buf_pool_mutex | 111264 |
| 13 | 2259 | wait/synch/mutex/innodb/fil_system_mutex | 8708688 |
| 13 | 2258 | wait/synch/mutex/innodb/buf_dblwr_mutex | 43776 |
| 13 | 2267 | wait/synch/mutex/innodb/flush_list_mutex | 28272 |
| 13 | 2266 | wait/synch/mutex/innodb/buf_pool_mutex | 60192 |
| 13 | 2265 | wait/synch/mutex/innodb/fil_system_mutex | 22800 |
| 13 | 2264 | wait/synch/mutex/innodb/flush_list_mutex | 29184 |
| 13 | 2263 | wait/synch/mutex/innodb/buf_pool_mutex | 23712 |
| 13 | 2262 | wait/synch/mutex/innodb/fil_system_mutex | 23712 |
| 13 | 2261 | wait/synch/mutex/innodb/flush_list_mutex | 122208 |
| 15 | 291 | wait/synch/mutex/innodb/buf_dblwr_mutex | 37392 |
+-----------+----------+------------------------------------------+------------+
21 rows in set (0.00 sec)
summary表提供所有事件的匯總信息。該組中的表以不同的方式匯總事件數據(如：按用戶，按主機，按線程等等)。例如：要查看哪些instruments占用最多的時間，可以通過對events_waits_summary_global_by_event_name表的COUNT_STAR或SUM_TIMER_WAIT列進行查詢(這兩列是對事件的記錄數執行COUNT(*)、事件記錄的TIMER_WAIT列執行SUM(TIMER_WAIT)統計而來)，如下：
qogir_env@localhost : performance_schema 06:17:23> SELECT EVENT_NAME,COUNT_STAR FROM events_waits_summary_global_by_event_name \
ORDER BY COUNT_STAR DESC LIMIT 10;
| EVENT_NAME | COUNT_STAR |
+---------------------------------------------------+------------+
| wait/synch/mutex/mysys/THR_LOCK_malloc | 6419 |
| wait/io/file/sql/FRM | 452 |
| wait/synch/mutex/sql/LOCK_plugin | 337 |
| wait/synch/mutex/mysys/THR_LOCK_open | 187 |
| wait/synch/mutex/mysys/LOCK_alarm | 147 |
| wait/synch/mutex/sql/THD::LOCK_thd_data | 115 |
| wait/io/file/myisam/kfile | 102 |
| wait/synch/mutex/sql/LOCK_global_system_variables | 89 |
| wait/synch/mutex/mysys/THR_LOCK::mutex | 89 |
| wait/synch/mutex/sql/LOCK_open | 88 |
+---------------------------------------------------+------------+
qogir_env@localhost : performance_schema 06:19:20> SELECT EVENT_NAME,SUM_TIMER_WAIT FROM events_waits_summary_global_by_event_name\
ORDER BY SUM_TIMER_WAIT DESC LIMIT 10;
+----------------------------------------+----------------+
| EVENT_NAME | SUM_TIMER_WAIT |
+----------------------------------------+----------------+
| wait/io/file/sql/MYSQL_LOG | 1599816582 |
| wait/synch/mutex/mysys/THR_LOCK_malloc | 1530083250 |
| wait/io/file/sql/binlog_index | 1385291934 |
| wait/io/file/sql/FRM | 1292823243 |
| wait/io/file/myisam/kfile | 411193611 |
| wait/io/file/myisam/dfile | 322401645 |
| wait/synch/mutex/mysys/LOCK_alarm | 145126935 |
| wait/io/file/sql/casetest | 104324715 |
| wait/synch/mutex/sql/LOCK_plugin | 86027823 |
| wait/io/file/sql/pid | 72591750 |
+----------------------------------------+----------------+
# 這些結果表明，THR_LOCK_malloc互斥事件是最熱的。注：THR_LOCK_malloc互斥事件僅在DEBUG版本中存在,GA版本不存在
instance表記錄了哪些類型的對象會被檢測。這些對象在被server使用時，在該表中將會產生一條事件記錄，例如，file_instances表列出了文件I/O操作及其關聯文件名：
qogir_env@localhost : performance_schema 06:27:26> SELECT * FROM file_instances limit 20;
+------------------------------------------------------+--------------------------------------+------------+
| FILE_NAME | EVENT_NAME | OPEN_COUNT |
+------------------------------------------------------+--------------------------------------+------------+
| /home/mysql/program/share/english/errmsg.sys | wait/io/file/sql/ERRMSG | 0 |
| /home/mysql/program/share/charsets/Index.xml | wait/io/file/mysys/charset | 0 |
| /data/mysqldata1/innodb_ts/ibdata1 | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/innodb_log/ib_logfile0 | wait/io/file/innodb/innodb_log_file | 2 |
| /data/mysqldata1/innodb_log/ib_logfile1 | wait/io/file/innodb/innodb_log_file | 2 |
| /data/mysqldata1/undo/undo001 | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/undo/undo002 | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/undo/undo003 | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/undo/undo004 | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/multi_master/test.ibd | wait/io/file/innodb/innodb_data_file | 1 |
| /data/mysqldata1/mydata/mysql/engine_cost.ibd | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/mysql/gtid_executed.ibd | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/mysql/help_category.ibd | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/mysql/help_keyword.ibd | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/mysql/help_relation.ibd | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/mysql/help_topic.ibd | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/mysql/innodb_index_stats.ibd | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/mysql/innodb_table_stats.ibd | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/mysql/plugin.ibd | wait/io/file/innodb/innodb_data_file | 3 |
| /data/mysqldata1/mydata/mysql/server_cost.ibd | wait/io/file/innodb/innodb_data_file | 3 |
+------------------------------------------------------+--------------------------------------+------------+
20 rows in set (0.00 sec)
setup_*是配置表，用于配置需要監視的事件類型、監視器的時間單位以及監視數據是否需要記錄在相關的表中以便查詢使用等，如下
# 要查看哪些可用事件計時器，可以查詢setup_timers表：
qogir_env@localhost : performance_schema 06:27:28> SELECT * FROM setup_timers;
+-------------+-------------+
| NAME | TIMER_NAME |
+-------------+-------------+
| idle | MICROSECOND |
| wait | CYCLE |
| stage | NANOSECOND |
| statement | NANOSECOND |
| transaction | NANOSECOND |
+-------------+-------------+
5 rows in set (0.00 sec)
# 要查看支持哪些事件收集instruments，以及哪些instruments被關閉或者被啟動，可以查看setup_instruments表(如果要啟用對應的監視器，則可以使用update語句更新ENABLED列為YES，要關閉則更新為NO。如果要啟用對應監視器的時間統計功能，則可以使用update語句更新TIMED列為YES，要關閉則更新為NO)
qogir_env@localhost : performance_schema 06:35:46> SELECT * FROM setup_instruments;
+---------------------------------------------------------+---------+-------+
| NAME | ENABLED | TIMED |
+---------------------------------------------------------+---------+-------+
| wait/synch/mutex/sql/TC_LOG_MMAP::LOCK_tc | YES | YES |
| wait/synch/mutex/sql/LOCK_des_key_file | YES | YES |
| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_commit | YES | YES |
| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_commit_queue | YES | YES |
| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_done | YES | YES |
| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_flush_queue | YES | YES |
| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_index | YES | YES |
| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_log | YES | YES |
| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_binlog_end_pos | YES | YES |
| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_sync | YES | YES |
......
| memory/sql/udf_mem | NO | NO |
| memory/sql/Relay_log_info::mts_coor | NO | NO |
| wait/lock/metadata/sql/mdl | YES | YES |
+--------------------------------------------------------------------------------+---------+-------+
1028 rows in set (0.00 sec)
# performance_schema使用instruments收集到的事件來更新performance_schema數據庫中的相關表，這些表充當instruments收集到的事件信息的“消費者”(consumers)，setup_consumers表列出了支持的consumers，哪些被關閉了，哪些啟用了(注：summary匯總表是否記錄數據由配置記錄global_instrumentation控制)，要啟用對應的consumers，則可以使用update語句更新ENABLED列為YES，要關閉則更新為NO
qogir_env@localhost : performance_schema 06:36:39> select * from setup_consumers;
+----------------------------------+---------+
| NAME | ENABLED |
+----------------------------------+---------+
| events_stages_current | YES |
| events_stages_history | YES |
| events_stages_history_long | YES |
| events_statements_current | YES |
| events_statements_history | YES |
| events_statements_history_long | NO |
| events_transactions_current | NO |
| events_transactions_history | NO |
| events_transactions_history_long | NO |
| events_waits_current | YES |
| events_waits_history | YES |
| events_waits_history_long | YES |
| global_instrumentation | YES |
| thread_instrumentation | YES |
| statements_digest | YES |
+----------------------------------+---------+
15 rows in set (0.00 sec)
有一些雜項表不屬于前面提到的任何分組。例如，performance_timers列出了可用的事件計時器及其特性
qogir_env@localhost : performance_schema 06:37:14> select * from performance_timers;
+-------------+-----------------+------------------+----------------+
| TIMER_NAME | TIMER_FREQUENCY | TIMER_RESOLUTION | TIMER_OVERHEAD |
+-------------+-----------------+------------------+----------------+
| CYCLE | 3292298507 | 1 | 21 |
| NANOSECOND | 1000000000 | 1 | 378 |
| MICROSECOND | 1000000 | 1 | 378 |
| MILLISECOND | 1035 | 1 | 378 |
| TICK | 106 | 1 | 345 |
+-------------+-----------------+------------------+----------------+
5 rows in set (0.00 sec)
對于配置表的啟用與禁用，如果通過直接修改setup_*這些表，在數據庫重啟之后，配置信息將丟失，如果需要長期保持這些配置，可以通過一些啟動選項進行配置，如
performance_schema_consumer_events_stages_current=FALSE
performance_schema_consumer_events_stages_history=FALSE
performance_schema_consumer_events_stages_history_long=FALSE
performance_schema_consumer_events_statements_current=TRUE
performance_schema_consumer_events_statements_history=TRUE
performance_schema_consumer_events_statements_history_long=FALSE
performance_schema_consumer_events_transactions_current=FALSE
performance_schema_consumer_events_transactions_history=FALSE
performance_schema_consumer_events_transactions_history_long=FALSE
performance_schema_consumer_events_waits_current=FALSE
performance_schema_consumer_events_waits_history=FALSE
performance_schema_consumer_events_waits_history_long=FALSE
performance_schema_consumer_global_instrumentation=TRUE
performance_schema_consumer_statements_digest=TRUE
performance_schema_consumer_thread_instrumentation=TRUE
performance_schema_instrument[=name] #name指定在instruments表中的name名稱，可以使用通配符%和_，詳見鏈接：https://dev.mysql.com/doc/refman/5.7/en/performance-schema-startup-configuration.html，或者詳見后續章節
總結
以上是生活随笔為你收集整理的mysql show schema_快速入门 · xiaoboluo768/mysql-system-schema Wiki · GitHub的全部內容，希望文章能夠幫你解決所遇到的問題。
- 上一篇： java线程组 线程池_JAVA多线程（
- 下一篇： python中打开文件提示编码当时错误_