mysqldump: Couldn't execute 'SAVEPOINT sp'

csdnhadoop

于 2017-02-21 21:40:47 发布

阅读量1.9k

点赞数 1

CC 4.0 BY-SA版权

本文链接：https://blog.youkuaiyun.com/csdnhadoop/article/details/56309282

本文解决了一个在使用mysqldump进行数据库备份时遇到的问题，即因服务器运行选项导致无法执行SAVEPOINT指令。通过调整transaction_write_set_extraction参数为OFF状态解决了这一问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

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)

解决办法：set global transaction_write_set_extraction=off; --Reserved for future use.

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