konstantin@mysql.com 55d148c5c2 A fix for Bug#19022 "Memory bug when switching db during trigger execution". ...

No test case as the bug is in an existing test case (rpl_trigger.test
when it is run under valgrind).
The warning was caused by memory corruption in replication slave: thd->db
was pointing at a stack address that was previously used by 
sp_head::execute()::old_db. This happened because mysql_change_db
behaved differently in replication slave and did not make a copy of the 
argument to assign to thd->db. 
The solution is to always free the old value of thd->db and allocate a new
copy, regardless whether we're running in a replication slave or not.

2006-06-28 23:47:45 +04:00

33 KiB

Raw Blame History

View Raw