Details
Critical
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/3382/steps/test_2/logs/stdio
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/2885/steps/test_2/logs/stdio
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/2885/steps/test_3/logs/stdio
The failure was introduced with the following revision:
revno: 4428
revision-id: sergii@pisem.net-20140930135502-azxpzckb86dmpo1f
parent: svoj@mariadb.org-20141003133846-h7cjr7mbk653q450
committer: Sergei Golubchik <sergii@pisem.net>
branch nick: 10.0
timestamp: Tue 2014-09-30 15:55:02 +0200
message:
BUG#13627921 - MISSING FLAGS IN SQL_COMMAND_FLAGS MAY LEAD TO REPLICATION PROBLEMS
merge from MySQL-5.6, revision:
revno: 3677.2.1
committer: Alfranio Correia <alfranio.correia@oracle.com>
timestamp: Tue 2012-02-28 16:26:37 +0000
message:
BUG#13627921 - MISSING FLAGS IN SQL_COMMAND_FLAGS MAY LEAD TO REPLICATION PROBLEMS
Flags in sql_command_flags[command] are not correctly set for the following
commands:
. SQLCOM_SET_OPTION is missing CF_CAN_GENERATE_ROW_EVENTS;
. SQLCOM_BINLOG_BASE64_EVENT is missing CF_CAN_GENERATE_ROW_EVENTS;
. SQLCOM_REVOKE_ALL is missing CF_CHANGES_DATA;
. SQLCOM_CREATE_FUNCTION is missing CF_AUTO_COMMIT_TRANS;
This may lead to a wrong sequence of events in the binary log. To fix
the problem, we correctly set the flags in sql_command_flags[command].
Gliffy Diagrams
Attachments
Issue Links
- blocks
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Stalled
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
