diff options
author | Nisha Gopalakrishnan <nisha.gopalakrishnan@oracle.com> | 2019-04-17 15:36:29 +0530 |
---|---|---|
committer | Sergei Golubchik <serg@mariadb.org> | 2019-07-24 18:32:24 +0200 |
commit | 2536c0b1ebf6c5012ae34435d82fb2f5fa54aea5 (patch) | |
tree | eecff27ba9f10f9bcf1e36c9797a0f75f670c698 /COPYING | |
parent | 7473a71a282c47a1e95359c575089c8ef51caf56 (diff) | |
download | mariadb-git-2536c0b1ebf6c5012ae34435d82fb2f5fa54aea5.tar.gz |
BUG#28642318: POINT IN TIME RECOVERY USING MYSQLBINLOG BROKEN WITH TEMPORARY TABLE -> ERRORS
Analysis
========
Point in time recovery using mysqlbinlog containing queries
operating on temporary tables results in an error.
While writing the query log event in the binary log, the
thread id used for execution of DROP TABLE and DELETE commands
were incorrect. The thread variable 'thread_specific_used'
is used to determine whether a specific thread id is to used
while executing the statements i.e using 'SET
@@session.pseudo_thread_id'. This variable was not set
correctly for DROP TABLE query and was never set for DELETE
query. The thread id is important for temporary tables
since the tables are session specific. DROP TABLE and DELETE
queries executed using a wrong thread id resulted in errors
while applying the queries generated by mysqlbinlog utility.
Fix
===
Set the 'thread_specific_used' THD variable for DROP TABLE and
DELETE queries.
ReviewBoard: 21833
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions