Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions mysql-test/suite/events/events_restart.test
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@
call mtr.add_suppression('Column count of mysql.event is wrong. Expected .*, found .*\. The table is probably corrupted');
call mtr.add_suppression('Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler');
call mtr.add_suppression('Event Scheduler.*shutdown.*');
call mtr.add_suppression('Event Scheduler: error during compilation of');
call mtr.add_suppression('Event Scheduler:.*Query was empty');
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@varundeepsaini have you actually been able to reproduce this problem?

How did you come to conclusion that the problem is due to "corrupted mysql.event table (body column altered to longtext during the test)"?

If suspected alter "corrupts" mysql.event table, why the problem is sporadic, not persistent?

From what I can see alter you're referring to is executed in the middle of the test and it gets restored by rename table event_like to mysql.event. But event in question test.ev is only created at the end of the test. There're many other events created in between and they don't fall victim to this corruption.

--enable_query_log

let $collation_server=`select @@collation_server`;
Expand Down