Bug #109857 | Truncate table with foreign key crash replication. | ||
---|---|---|---|
Submitted: | 31 Jan 2023 8:55 | Modified: | 3 Feb 2023 4:54 |
Reporter: | Fengchun Hua | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 5.7.38 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | foreign key, Replicaiton |
[31 Jan 2023 8:55]
Fengchun Hua
[31 Jan 2023 9:05]
Fengchun Hua
Or truncate should lock both t1 and t2;
[31 Jan 2023 9:35]
Fengchun Hua
Can't reproduce in 8.0.25
[3 Feb 2023 4:54]
MySQL Verification Team
Hello Fengchun Hua, Thank you for the report and test case. IMHO this is duplicate of Bug #97836, please see Bug #97836. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. regards, Umesh