Bug #30648 | Partition handler may not initialize variable used w/ autoincrement | ||
---|---|---|---|
Submitted: | 27 Aug 2007 17:47 | Modified: | 31 Aug 2007 13:48 |
Reporter: | Timothy Smith | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Partitions | Severity: | S3 (Non-critical) |
Version: | 5.1 | OS: | Any |
Assigned to: | Timothy Smith | CPU Architecture: | Any |
[27 Aug 2007 17:47]
Timothy Smith
[27 Aug 2007 17:49]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/33164 ChangeSet@1.2576, 2007-08-27 11:46:34-06:00, tsmith@ramayana.hindu.god +1 -0 Bug #30648: Partition handler may not initialize variable used w/ autoincrement A local variable may be used uninitialized in ha_partition::get_auto_increment(). Initialize it properly.
[28 Aug 2007 16:56]
Trudy Pelzer
Patch has been pushed to 5.1.22 tree.
[28 Aug 2007 18:36]
Timothy Smith
Queued to target-5.1.22
[29 Aug 2007 18:55]
Timothy Smith
Docs team: I'm not aware of any release in which this bug would show up. It became visible only after some changes to InnoDB's auto-increment handling (see bug #16979), but I don't have a test case against any released version of MySQL which tickles this bug. So, it may not need to be documented. The symptom, by the way, was that partitioning an innodb table based on an auto_increment key failed to generate correct values for the key column. Instead, it would use the contents of some uninitialized variable, repeatedly (i.e., you get the same junk value over and over).
[31 Aug 2007 13:48]
Paul DuBois
No changelog entry needed.
[4 Sep 2007 17:11]
Bugs System
Pushed into 5.1.23-beta