mysqldump: Couldn't execute 'SAVEPOINT sp':
報錯信息
# 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,可以動態修改,未來組復制特性需要使用此參數。
本文轉自 roidba 51CTO博客,原文鏈接:http://blog.51cto.com/roidba/1875700,如需轉載請自行聯系原作者
總結
以上是生活随笔為你收集整理的mysqldump: Couldn't execute 'SAVEPOINT sp':的全部內容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: 【线性规划与网络流24题】孤岛营救问题
- 下一篇: 系统、网络运维好帮手:expect