database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-07-17 12:02:09 +03:00
Code Activity

MDEV-16708: fixed assert firing in the method THD::reset_for_the_next_command

Browse Source
This commit is contained in:
Dmitry Shulga
2021-06-11 11:25:56 +07:00
committed by Sergei Golubchik
parent 994e3f40b5
commit fe78495053
2 changed files with 48 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
sql/sql_binlog.cc
View File

@ -354,8 +354,28 @@ void mysql_client_binlog_statement(THD* thd)
(ev->flags & LOG_EVENT_SKIP_REPLICATION_F ?
OPTION_SKIP_REPLICATION : 0);
err= ev->apply_event(rgi);
{
/*
For conventional statements thd->lex points to thd->main_lex, that is
thd->lex == &thd->main_lex. On the other hand, for prepared statement
thd->lex points to the LEX object explicitly allocated for execution
of the prepared statement and in this case thd->lex != &thd->main_lex.
On handling the BINLOG statement, invocation of ev->apply_event(rgi)
initiates the following sequence of calls
Rows_log_event::do_apply_event -> THD::reset_for_next_command
Since the method THD::reset_for_next_command() contains assert
DBUG_ASSERT(lex == &main_lex)
this sequence of calls results in crash when a binlog event is
applied in PS mode. So, reset the current lex temporary to point to
thd->main_lex before running ev->apply_event() and restore its
original value on return.
*/
LEX *backup_lex;
thd->backup_and_reset_current_lex(&backup_lex);
err= ev->apply_event(rgi);
thd->restore_current_lex(backup_lex);
}
thd->variables.option_bits=
(thd->variables.option_bits & ~OPTION_SKIP_REPLICATION) |
save_skip_replication;