mysqldump: Couldn't execute 'SAVEPOINT sp':

Posted 2020-08-20

1. 报错信息

# mysqldump --default-character-set=utf8 --set-gtid-purged=on  -uxx -pxx -hx.x.x.x  --triggers --routines --events --single-transaction --databases xx  >./bak_xx_$(date +%F).sql

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

Warning: A partial dump from a server that has GTIDs will by default include the GTIDs of all transactions, even those that changed suppressed parts of the database. If you don‘t want to restore GTIDs, pass --set-gtid-purged=OFF. To make a complete dump, pass --all-databases --triggers --routines --events. 

mysqldump: Couldn‘t execute ‘SAVEPOINT sp‘: 

The MySQL server is running with the --transaction-write-set-extraction!=OFF option so it cannot execute this statement (1290)

2.处理方法

> set global transaction_write_set_extraction=off;   --Reserved for future use.

Query OK, 0 rows affected (0.00 sec)

3.总结

数据库版本5.7.15 ，备份的时候报错，根据报错信息到官网查看相关参数含义。以上参数未来使用预留，默认是为Off，可以动态修改，未来组复制特性需要使用此参数。

本文出自 “12318731” 博客，请务必保留此出处http://12328731.blog.51cto.com/12318731/1875700