作为 MySQL DBA ，相信大家都经历过在复制模式下，如果没有主键，遇到 load data ，大事务，ddl 等有大量表数据行扫描的行为时，会带来严重的主从延迟，给数据库稳定性和数据一致性带来隐患。例如：https://www.xmmup.com/dbbao34ceshimysqlzhucongfuzhizhongzhukubiaoqueshizhujianhuidaozhizhu.html

从MySQL 8.0.30 开始，提出了一个令人惊喜的特性 -（Generated Invisible Primary Keys）简称 GIPK 。一句概况就是: 当开启GIPK模式后，MySQL 会在没有显示定义主键的InnoDB表上自动生成不可见的主键。

对于已经使用云RDS的朋友，可能很早就享受到云 RDS MySQL 提供的隐式主键特性。但是对于自建数据库的企业，GIPK 依然是一个比较期待特性，（当然有和用起来是两码事！）

示例

环境

mkdir -p /etc/mysql/mysql8030/conf/
cat >  /etc/mysql/mysql8030/conf/my.cnf <<"EOF"
[mysqld]
default-time-zone = '+8:00'
log_timestamps = SYSTEM
skip-name-resolve
log-bin
server_id=803430
character_set_server=utf8mb4
EOF

docker run -d --name mysql8030 -h mysql8030 -p 3430:3306 \
  -v /etc/mysql/mysql8030/conf:/etc/mysql/conf.d \
  -e MYSQL_ROOT_PASSWORD=lhr -e TZ=Asia/Shanghai \
  mysql:8.0.30

[root@docker35 ~]# mysql -uroot -plhr -h127.0.0.1 -P3430
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 8
Server version: 8.0.30 MySQL Community Server - GPL

Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mkdir -p /etc/mysql/mysql8030/conf/

cat > /etc/mysql/mysql8030/conf/my.cnf <<"EOF"

[mysqld]

default-time-zone = '+8:00'

log_timestamps = SYSTEM

skip-name-resolve

log-bin

server_id=803430

character_set_server=utf8mb4

EOF

docker run -d --name mysql8030 -h mysql8030 -p 3430:3306 \

-v /etc/mysql/mysql8030/conf:/etc/mysql/conf.d \

-e MYSQL_ROOT_PASSWORD=lhr -e TZ=Asia/Shanghai \

mysql:8.0.30

[root@docker35 ~]# mysql -uroot -plhr -h127.0.0.1 -P3430

mysql: [Warning] Using a password on the command line interface can be insecure.

Welcome to the MySQL monitor. Commands end with ; or \g.

Your MySQL connection id is 8

Server version: 8.0.30 MySQL Community Server - GPL

Oracle is a registered trademark of Oracle Corporation and/or its

affiliates. Other names may be trademarks of their respective

owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

开启新特性

GIPK 由参数sql_generate_invisible_primary_key 控制，默认关闭，表示禁用，如果需要使用该特性，则需显式开启。

mysql> show variables like 'sql_generate_invisible_primary_key';
+------------------------------------+-------+
| Variable_name                      | Value |
+------------------------------------+-------+
| sql_generate_invisible_primary_key | OFF   |
+------------------------------------+-------+
1 row in set (0.00 sec)

mysql> set sql_generate_invisible_primary_key=on;
Query OK, 0 rows affected (0.00 sec)

mysql> show variables like 'sql_generate_invisible_primary_key';
+------------------------------------+-------+
| Variable_name                      | Value |
+------------------------------------+-------+
| sql_generate_invisible_primary_key | ON    |
+------------------------------------+-------+
1 row in set (0.00 sec)

mysql> show variables like 'sql_generate_invisible_primary_key';

+------------------------------------+-------+

| Variable_name | Value |

+------------------------------------+-------+

| sql_generate_invisible_primary_key | OFF |

+------------------------------------+-------+

1 row in set (0.00 sec)

mysql> set sql_generate_invisible_primary_key=on;

Query OK, 0 rows affected (0.00 sec)

mysql> show variables like 'sql_generate_invisible_primary_key';

+------------------------------------+-------+

| Variable_name | Value |

+------------------------------------+-------+

| sql_generate_invisible_primary_key | ON |

+------------------------------------+-------+

1 row in set (0.00 sec)

测试

我们分别在关闭和开启该特性下创建两个无主键表:

mysql> create table t1(id int ,c1 int);
Query OK, 0 rows affected (0.00 sec)
master [localhost:22031] {msandbox} (test) > show create table t1 \G
*************************** 1. row ***************************
       Table: t1
Create Table: CREATE TABLE `t1` (
  `id` int DEFAULT NULL,
  `c1` int DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (0.00 sec)

mysql> create table t1(id int ,c1 int);

Query OK, 0 rows affected (0.00 sec)

master [localhost:22031] {msandbox} (test) > show create table t1 \G

*************************** 1. row ***************************

Table: t1

Create Table: CREATE TABLE `t1` (

`id` int DEFAULT NULL,

`c1` int DEFAULT NULL

) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

1 row in set (0.00 sec)

开启 GIPK 并创建无主键表 t3 。

mysql> set sql_generate_invisible_primary_key=on;
Query OK, 0 rows affected (0.00 sec)

master [localhost:22031] {msandbox} (test) > show variables like 'sql_generate_invisible_primary_key';
+------------------------------------+-------+
| Variable_name                      | Value |
+------------------------------------+-------+
| sql_generate_invisible_primary_key | ON    |
+------------------------------------+-------+
1 row in set (0.00 sec)

mysql> create table t3(id int ,c1 int);
Query OK, 0 rows affected (0.01 sec)

master [localhost:22031]>
mysql> show create table t3 \G
*************************** 1. row ***************************
       Table: t3
Create Table: CREATE TABLE `t3` (
  `my_row_id` bigint unsigned NOT NULL AUTO_INCREMENT /*!80023 INVISIBLE */,
  `id` int DEFAULT NULL,
  `c1` int DEFAULT NULL,
  PRIMARY KEY (`my_row_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (0.00 sec)
mysql> desc t3;
+-----------+-----------------+------+-----+---------+--------------------------+
| Field     | Type            | Null | Key | Default | Extra                    |
+-----------+-----------------+------+-----+---------+--------------------------+
| my_row_id | bigint unsigned | NO   | PRI | NULL    | auto_increment INVISIBLE |
| id        | int             | YES  |     | NULL    |                          |
| c1        | int             | YES  |     | NULL    |                          |
+-----------+-----------------+------+-----+---------+--------------------------+
3 rows in set (0.00 sec)

mysql> set sql_generate_invisible_primary_key=on;

Query OK, 0 rows affected (0.00 sec)

master [localhost:22031] {msandbox} (test) > show variables like 'sql_generate_invisible_primary_key';

+------------------------------------+-------+

| Variable_name | Value |

+------------------------------------+-------+

| sql_generate_invisible_primary_key | ON |

+------------------------------------+-------+

1 row in set (0.00 sec)

mysql> create table t3(id int ,c1 int);

Query OK, 0 rows affected (0.01 sec)

master [localhost:22031]>

mysql> show create table t3 \G

*************************** 1. row ***************************

Table: t3

Create Table: CREATE TABLE `t3` (

`my_row_id` bigint unsigned NOT NULL AUTO_INCREMENT /*!80023 INVISIBLE */,

`id` int DEFAULT NULL,

`c1` int DEFAULT NULL,

PRIMARY KEY (`my_row_id`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

1 row in set (0.00 sec)

mysql> desc t3;

+-----------+-----------------+------+-----+---------+--------------------------+

+-----------+-----------------+------+-----+---------+--------------------------+

| id | int | YES | | NULL | |

| c1 | int | YES | | NULL | |

+-----------+-----------------+------+-----+---------+--------------------------+

3 rows in set (0.00 sec)

我们可以通过 show create table 发现 t3 的表结构，出现名为 my_row_id 的不可见主键。对两个表插入数据查看差异:

mysql> insert into t1 values(1,1),(2,2),(3,3);
Query OK, 3 rows affected (0.00 sec)
Records: 3  Duplicates: 0  Warnings: 0
mysql> select * from t1;
+------+------+
| id   | c1   |
+------+------+
|    1 |    1 |
|    2 |    2 |
|    3 |    3 |
+------+------+
3 rows in set (0.00 sec)
mysql> insert into t3 values(1,1),(2,2),(3,3);
Query OK, 3 rows affected (0.00 sec)
Records: 3  Duplicates: 0  Warnings: 0
mysql> select * from t3;
+------+------+
| id   | c1   |
+------+------+
|    1 |    1 |
|    2 |    2 |
|    3 |    3 |
+------+------+
3 rows in set (0.00 sec)

mysql> insert into t1 values(1,1),(2,2),(3,3);

Query OK, 3 rows affected (0.00 sec)

Records: 3 Duplicates: 0 Warnings: 0

mysql> select * from t1;

+------+------+

| id | c1 |

+------+------+

| 1 | 1 |

| 2 | 2 |

| 3 | 3 |

+------+------+

3 rows in set (0.00 sec)

mysql> insert into t3 values(1,1),(2,2),(3,3);

Query OK, 3 rows affected (0.00 sec)

Records: 3 Duplicates: 0 Warnings: 0

mysql> select * from t3;

+------+------+

| id | c1 |

+------+------+

| 1 | 1 |

| 2 | 2 |

| 3 | 3 |

+------+------+

3 rows in set (0.00 sec)

直接通过 select * from table 查询时，t3 和普通表t1无差异。因为 GIPK 是基于不可见列实现的，如果我们显式指定访问 my_row_id ,则可以查看到隐藏的主键 my_row_id。

mysql> select my_row_id,id,c1 from t3;
+-----------+------+------+
| my_row_id | id   | c1   |
+-----------+------+------+
|         1 |    1 |    1 |
|         2 |    2 |    2 |
|         3 |    3 |    3 |
+-----------+------+------+
3 rows in set (0.00 sec)

mysql> select my_row_id,id,c1 from t3;

+-----------+------+------+

| my_row_id | id | c1 |

+-----------+------+------+

| 1 | 1 | 1 |

| 2 | 2 | 2 |

| 3 | 3 | 3 |

+-----------+------+------+

3 rows in set (0.00 sec)

总的来说，从业务程序访问数据库的角度来看，开启 GIPK 对业务是透明的。

关于 DDL

当开启 GIPK 特性时，MySQL 生成的主键不能更改，只能在 VISIBLE 和 INVISIBLE 之间进行切换。比如：

使 GIPK 主键可见: alter table TALBE_NAME alter column my_row_id set visible；

mysql> alter table t3 alter column my_row_id set visible;
Query OK, 0 rows affected (0.01 sec)
Records: 0  Duplicates: 0  Warnings: 0
mysql> show create table t3 \G
*************************** 1. row ***************************
       Table: t3
Create Table: CREATE TABLE `t3` (
  `my_row_id` bigint unsigned NOT NULL AUTO_INCREMENT, ### 显式可见 
  `id` int DEFAULT NULL,
  `c1` int DEFAULT NULL,
  PRIMARY KEY (`my_row_id`)
) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (0.00 sec)

### 而且可以被直接查询到
mysql> select * from t3;
+-----------+------+------+
| my_row_id | id   | c1   |
+-----------+------+------+
|         1 |    1 |    1 |
|         2 |    2 |    2 |
|         3 |    3 |    3 |
+-----------+------+------+
3 rows in set (0.00 sec)

mysql> alter table t3 alter column my_row_id set visible;

Query OK, 0 rows affected (0.01 sec)

Records: 0 Duplicates: 0 Warnings: 0

mysql> show create table t3 \G

*************************** 1. row ***************************

Table: t3

Create Table: CREATE TABLE `t3` (

`my_row_id` bigint unsigned NOT NULL AUTO_INCREMENT, ### 显式可见

`id` int DEFAULT NULL,

`c1` int DEFAULT NULL,

PRIMARY KEY (`my_row_id`)

) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

1 row in set (0.00 sec)

### 而且可以被直接查询到

mysql> select * from t3;

+-----------+------+------+

| my_row_id | id | c1 |

+-----------+------+------+

| 1 | 1 | 1 |

| 2 | 2 | 2 |

| 3 | 3 | 3 |

+-----------+------+------+

3 rows in set (0.00 sec)

关闭起可见性 : alter table TABLE_NAME alter column my_row_id set invisible;

mysql> alter table t3 alter column my_row_id set invisible;
Query OK, 0 rows affected (0.00 sec)
Records: 0  Duplicates: 0  Warnings: 0
mysql> show create table t3 \G
*************************** 1. row ***************************
       Table: t3
Create Table: CREATE TABLE `t3` (
  `my_row_id` bigint unsigned NOT NULL AUTO_INCREMENT /*!80023 INVISIBLE */,
  `id` int DEFAULT NULL,
  `c1` int DEFAULT NULL,
  PRIMARY KEY (`my_row_id`)
) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (0.00 sec)
## 再次通过select * 查询则看不到 my_row_id
mysql> select * from t3;
+------+------+
| id   | c1   |
+------+------+
|    1 |    1 |
|    2 |    2 |
|    3 |    3 |
+------+------+
3 rows in set (0.00 sec)

mysql> alter table t3 alter column my_row_id set invisible;

Query OK, 0 rows affected (0.00 sec)

Records: 0 Duplicates: 0 Warnings: 0

mysql> show create table t3 \G

*************************** 1. row ***************************

Table: t3

Create Table: CREATE TABLE `t3` (

`my_row_id` bigint unsigned NOT NULL AUTO_INCREMENT /*!80023 INVISIBLE */,

`id` int DEFAULT NULL,

`c1` int DEFAULT NULL,

PRIMARY KEY (`my_row_id`)

) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

1 row in set (0.00 sec)

## 再次通过select * 查询则看不到 my_row_id

mysql> select * from t3;

+------+------+

| id | c1 |

+------+------+

| 1 | 1 |

| 2 | 2 |

| 3 | 3 |

+------+------+

3 rows in set (0.00 sec)

另外就是开启 GIPK 之后，my_row_id 是系统关键字，我们创建无主键的表时，不能包含名为 my_row_id 的字段。

mysql> create table t6(my_row_id int not null   ,c1 int);
ERROR 4108 (HY000): Failed to generate invisible primary key. Column 'my_row_id' already exists.

1 2	mysql> create table t6(my_row_id int not null ,c1 int); ERROR 4108 (HY000): Failed to generate invisible primary key. Column 'my_row_id' already exists.

本人提供Oracle(OCP、OCM)、MySQL(OCP)、PostgreSQL(PGCA、PGCE、PGCM)等数据库的培训和考证业务，私聊QQ646634621或微信db_bao，谢谢！

当然如果 MySQL 允许创建包含名为 my_row_id 的主键的表：

mysql> create table t5(my_row_id int not null auto_increment primary key  ,c1 int);
Query OK, 0 rows affected (0.01 sec)

1 2	mysql> create table t5(my_row_id int not null auto_increment primary key ,c1 int); Query OK, 0 rows affected (0.01 sec)

当开启 GIPK 模式时，则不能直接删除不可见主键，必须显式增加一个新的主键然后再删除 GIPK，如下：

mysql> alter table t3 add PRIMARY KEY(id);
ERROR 1068 (42000): Multiple primary key defined

mysql> alter table t3 drop PRIMARY KEY;
ERROR 1235 (42000): This version of MySQL doesn't yet support 'existing primary key drop without adding a new primary key. In @@sql_generate_invisible_primary_key=ON mode table should have a primary key. Please add a new primary key to be able to drop existing primary key.'

mysql> alter table t3 drop PRIMARY KEY,add primary key(id);
ERROR 4111 (HY000): Please drop primary key column to be able to drop generated invisible primary key.

mysql> alter table t3 drop column my_row_id,add primary key(id);
Query OK, 0 rows affected (0.02 sec)
Records: 0  Duplicates: 0  Warnings: 0

mysql> alter table t3 add PRIMARY KEY(id);

ERROR 1068 (42000): Multiple primary key defined

mysql> alter table t3 drop PRIMARY KEY;

ERROR 1235 (42000): This version of MySQL doesn't yet support 'existing primary key drop without adding a new primary key. In @@sql_generate_invisible_primary_key=ON mode table should have a primary key. Please add a new primary key to be able to drop existing primary key.'

mysql> alter table t3 drop PRIMARY KEY,add primary key(id);

ERROR 4111 (HY000): Please drop primary key column to be able to drop generated invisible primary key.

mysql> alter table t3 drop column my_row_id,add primary key(id);

Query OK, 0 rows affected (0.02 sec)

Records: 0 Duplicates: 0 Warnings: 0

关于主从复制

需要注意的是 set sql_generate_invisible_primary_key=on|off 并不会被复制到从库，主库上开启该特性的话，从库并不会开启 GIPK 。也就是说从库也不会为任何在源库上没有创建主键的表创建主键。可能会有读者疑问如果主库关闭该特性，但是从库显示开启呢？ 做个测试看看：

在 master 上关闭该特性并且创建无主键表t6

mysql> set sql_generate_invisible_primary_key=off;
Query OK, 0 rows affected (0.00 sec)
master [localhost:22031]>
master [localhost:22031]>show variables like 'sql_generate_invisible_primary_key';
+------------------------------------+-------+
| Variable_name                      | Value |
+------------------------------------+-------+
| sql_generate_invisible_primary_key | OFF   |
+------------------------------------+-------+
1 row in set (0.00 sec)

mysql> show tables;
+----------------+
| Tables_in_test |
+----------------+
| t1             |
| t2             |
| t3             |
| t4             |
| t5             |
+----------------+
5 rows in set (0.00 sec)

mysql> create table t6(id int ,c1 int);
Query OK, 0 rows affected (0.01 sec)

mysql> show create table t6\G
*************************** 1. row ***************************
       Table: t6
Create Table: CREATE TABLE `t6` (
  `id` int DEFAULT NULL,
  `c1` int DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (0.00 sec)

mysql> set sql_generate_invisible_primary_key=off;

Query OK, 0 rows affected (0.00 sec)

master [localhost:22031]>

master [localhost:22031]>show variables like 'sql_generate_invisible_primary_key';

+------------------------------------+-------+

| Variable_name | Value |

+------------------------------------+-------+

| sql_generate_invisible_primary_key | OFF |

+------------------------------------+-------+

1 row in set (0.00 sec)

mysql> show tables;

+----------------+

| Tables_in_test |

+----------------+

| t1 |

| t2 |

| t3 |

| t4 |

| t5 |

+----------------+

5 rows in set (0.00 sec)

mysql> create table t6(id int ,c1 int);

Query OK, 0 rows affected (0.01 sec)

mysql> show create table t6\G

*************************** 1. row ***************************

Table: t6

Create Table: CREATE TABLE `t6` (

`id` int DEFAULT NULL,

`c1` int DEFAULT NULL

) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

1 row in set (0.00 sec)

在从库上开启该特性

slave1 [localhost:22032]> show tables;
+----------------+
| Tables_in_test |
+----------------+
| t1             |
| t2             |
| t3             |
| t4             |
| t5             |
+----------------+
5 rows in set (0.00 sec)
slave1 [localhost:22032]> set sql_generate_invisible_primary_key=on;
Query OK, 0 rows affected (0.00 sec)
slave1 [localhost:22032]> show variables like 'sql_generate_invisible_primary_key';
+------------------------------------+-------+
| Variable_name                      | Value |
+------------------------------------+-------+
| sql_generate_invisible_primary_key | ON    |
+------------------------------------+-------+
1 row in set (0.00 sec)
slave1 [localhost:22032]> show create table t6\G
*************************** 1. row ***************************
       Table: t6
Create Table: CREATE TABLE `t6` (
  `id` int DEFAULT NULL,
  `c1` int DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (0.00 sec)

slave1 [localhost:22032]> show tables;

+----------------+

| Tables_in_test |

+----------------+

| t1 |

| t2 |

| t3 |

| t4 |

| t5 |

+----------------+

5 rows in set (0.00 sec)

slave1 [localhost:22032]> set sql_generate_invisible_primary_key=on;

Query OK, 0 rows affected (0.00 sec)

slave1 [localhost:22032]> show variables like 'sql_generate_invisible_primary_key';

+------------------------------------+-------+

| Variable_name | Value |

+------------------------------------+-------+

| sql_generate_invisible_primary_key | ON |

+------------------------------------+-------+

1 row in set (0.00 sec)

slave1 [localhost:22032]> show create table t6\G

*************************** 1. row ***************************

Table: t6

Create Table: CREATE TABLE `t6` (

`id` int DEFAULT NULL,

`c1` int DEFAULT NULL

) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

1 row in set (0.00 sec)

结果: 主库关闭 GIPK ，从库开启 GIPK ，源库上创建无主键表，从库上并不会主动为该表创建主键。

逻辑备份

大多数实例会进行逻辑备份，如果开启GIPK 模式时，MySQL 8.0.30 版本的 mysqldump 提供的 --skip-generated-invisible-primary-key 选项会忽略 GIPK 信息。简单来说，mysqldump 时不带该参数，逻辑导出的数据会包含隐式主键，如果带上该参数，则不带隐式主键。

限制

只支持 InnoDB 存储引擎。
支持 row 模式复制，不支持 statement 模式复制。
my_row_id 成为系统关键字。

参考文档

https://mp.weixin.qq.com/s/72MmKRIxdz3zkwjdu4_lEw

https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html

https://dev.mysql.com/doc/refman/8.0/en/invisible-columns.html

打赏赞(3)

标签： GIPK不可见主键 MySQL sql_generate_invisible_primary_key 新特性

小麦苗

学习或考证，均可联系麦老师，请加微信db_bao或QQ646634621

发表回复取消回复

要发表评论，您必须先登录。

2023年 3月
一	二	三	四	五	六	日
	1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31

嘿，我是小麦，需要帮助随时找我哦

18509239930
个人微信
麦老师QQ聊天
个人邮箱
点击加入QQ群
个人微店
回到顶部

小麦苗

MySQL 8.0.30新特性之GIPK不可见主键sql_generate_invisible_primary_key

简介

示例

环境

开启新特性

测试

关于 DDL

关于主从复制

逻辑备份

限制

参考文档

相关文章

您可能还喜欢...

发表回复取消回复

博客寄语

博客概况

本站其它工具

搜标题

搜索本网站

标签云☁

登陆本博客

博客日历

博客归档

博客分类

MySQL 8.0.30新特性之GIPK不可见主键sql_generate_invisible_primary_key

简介

示例

环境

开启新特性

测试

关于 DDL

关于主从复制

逻辑备份

限制

参考文档

相关文章

您可能还喜欢...

分别在MySQL5.7和8.0中测试主从复制中主库表缺失主键会导致主从延迟的情况

MySQL磁盘IO巨高排查全过程

是什么导致MySQL数据库服务器磁盘IO高？

发表回复 取消回复

博客寄语

博客概况

本站其它工具

搜标题

搜索本网站

标签云☁

登陆本博客

博客日历

博客归档

博客分类

发表回复取消回复