Bug #4125 crash while updating using 2 indexes
Submitted: 14 Jun 2004 11:52 Modified: 26 Sep 2005 15:56
Reporter: Stefan Dombrowski Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.0.0-0 OS:Linux (Linux (SuSE 9.0))
Assigned to: CPU Architecture:Any

[14 Jun 2004 11:52] Stefan Dombrowski
Description:
MySQL server crashed on update statement when 2 indexes are used

update mail set reject_sorbs='Y' where client = '0-1pool138-227.nas10.tukwila2.wa.us.da.qwest.net' or ip = '67.5.138.227' ;

index on both client and ip => crash
index on none or only one of those fields => OK
indexes on fields other than client & IP => no effect (crash if client / ip index)

migrated table from idam to InoDB => same problem

How to repeat:
crashes on every update statement when indexes are present
[14 Jun 2004 12:10] Stefan Dombrowski
could not send full export - but found "crashing" subset of 1200 rows instead of 131000

- same error, same SQL statement
[15 Aug 2005 14:43] Islam Mayer
Version 5.0.0 is way to old. There is no reasons to play with it. Colud you please try to reproduce it with more recent version?
Thank you.

--
emai: Islam S. Mayer <islammayer@gmail.com>
site: http://www.emistry.com/
[26 Aug 2005 15:56] Valeriy Kravchuk
Thank you for taking the time to report a problem.  Unfortunately
you are not using a current version of the product your reported a
problem with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions,
please change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for
your continued support of MySQL.

Additional info:

Have you tried recent versions of MySQL 5.0.x? 5.0.11? If bug remains, please, reopen it.
[26 Sep 2005 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".