Bug #5553 | UPDATE IGNORE with multiple tables can lock up mysqld connection,reproducable | ||
---|---|---|---|
Submitted: | 13 Sep 2004 22:31 | Modified: | 23 Sep 2004 9:59 |
Reporter: | Miles Georgi | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.1.4 | OS: | Linux (Linux 2.4.20 debian) |
Assigned to: | Antony Curtis | CPU Architecture: | Any |
[13 Sep 2004 22:31]
Miles Georgi
[13 Sep 2004 23:06]
Miles Georgi
compressed script that reproduces bug
Attachment: ignorebug.sql.bz2 (application/octet-stream, text), 2.01 KiB.
[14 Sep 2004 8:41]
Miles Georgi
updated Synopsis to mention multiple tables
[14 Sep 2004 13:13]
MySQL Verification Team
Hi, Thank you for the bug report! I was able to reproduce the same behavior on 4.1.4 binary distribution. On the latest BK 4.1 tree I got error: mysql> UPDATE IGNORE table2,table1 set table2.colE = table2.colE + 1 WHERE table1.colA = table2.colA AND (table1.colB & 4096) > 0 AND (colE + 1) < colF; ERROR 1105 (HY000): Unknown error
[17 Sep 2004 0:54]
Antony Curtis
Patch for review: Subject: bk commit - 4.1 tree (antony:1.2013) BUG#5553 Date: Fri, 17 Sep 2004 01:46:51 +0100 (BST) ChangeSet 1.2013 04/09/17 01:46:49 antony@ltantony.rdg.cyberkinetica.homeunix.net +3 -0 Bug#5553 - Multi table UPDATE IGNORE fails on dup key We don't want the update to abort when IGNORE is specified
[17 Sep 2004 11:14]
Antony Curtis
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: Fix applied to MySQL 4.0 repository
[22 Sep 2004 1:18]
Miles Georgi
Hi, I noticed 4.1.5 came out and I don't see a post about this bug fix in the change log posted at http://lists.mysql.com/announce/222 just wanted to make sure that the fix is actually in this release and if so I will perform an upgrade tonight. Thank you for the very quick fix! miles
[22 Sep 2004 1:32]
Miles Georgi
Via Bit Keeper I see it in the 4.0 tree's change set but not in the 4.1 tree's changeset. I am assuming that 4.1 will be updated soon, is that correct? Just making sure it didn't slip through the cracks. miles
[23 Sep 2004 9:59]
Sergei Golubchik
Correct. It will be updated (at the latest) before the next 4.1 (or 5.0) release. As a part or the release procedure we merge all changes from 3.23 up to the tree we release (that means, for 5.0 release we merge 3.23->4.0->4.1->5.0)