Bug #46396 | returned MAX value of primary integer key is less than actual max value | ||
---|---|---|---|
Submitted: | 27 Jul 2009 9:20 | Modified: | 28 Jul 2009 5:14 |
Reporter: | ALex Lysenko | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.1.11 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | MAX |
[27 Jul 2009 9:20]
ALex Lysenko
[27 Jul 2009 9:28]
Sveta Smirnova
Thank you for the report. But version 5.1.11 is very old and many bugs were fixed since. Please try current version 5.1.36 and inform us if problem still exists. If you are using InnoDB tables check if inserted row was in uncommitted transaction also.
[27 Jul 2009 9:32]
ALex Lysenko
Sorry. Both in description and how to repeat, I forgot: comparing max1, max2 and max3 is performed, when the bug is revealed, i.e. when max1 < LastMsgNum
[27 Jul 2009 9:33]
ALex Lysenko
Thanks, I will try. I am using MyISAM with no transactions.
[27 Jul 2009 9:45]
Sveta Smirnova
Thank you for the feedback. We will wait results of your tests.
[28 Jul 2009 4:40]
ALex Lysenko
It seems that this bug is fixed in current version. I tried 5.1.34 - bug was not detected.
[28 Jul 2009 5:14]
Sveta Smirnova
Thank you for the feedback. Closed as "Can't repeat" because last comment.