Bug #11889 | Server crash when dropping a trigger using non-cached stored routine | ||
---|---|---|---|
Submitted: | 12 Jul 2005 16:28 | Modified: | 14 Jul 2005 15:41 |
Reporter: | Omer Barnir (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.0.10 | OS: | Linux (Linux / All) |
Assigned to: | Dmitry Lenev | CPU Architecture: | Any |
[12 Jul 2005 16:28]
Omer Barnir
[13 Jul 2005 1:18]
Omer Barnir
Additional information: The crash (when dropping the table) happens even if the stored procedure is not called. The crash does not happen if the the trigger is not defined
[13 Jul 2005 20:13]
Dmitry Lenev
Hi, Omer! Actually this bug has nothing to do with trigger recursivity. The simplified test case for this problem looks like: use test; drop table if exists t1_sp; create table t1_sp ( count integer, var136 tinyint, var151 decimal); create procedure trig_sp() begin end; create trigger trg before insert on t1_sp for each row call trig_sp(); # If procedure is not cached in sp-cache the following DROP TRIGGER will lead to crash. drop trigger t1_sp.trg; This bug was fixed by the same patch as bug #11554. Fixed in 5.0.10.
[14 Jul 2005 15:41]
Paul DuBois
Noted in 5.0.10 changelog.