Bug #17947 | Partitions: crash if rebuild with no name | ||
---|---|---|---|
Submitted: | 6 Mar 2006 2:08 | Modified: | 16 Mar 2006 8:27 |
Reporter: | Peter Gulutzan | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Partitions | Severity: | S3 (Non-critical) |
Version: | 5.1.8-beta-debug | OS: | Linux (SUSE 10.0) |
Assigned to: | Mikael Ronström | CPU Architecture: | Any |
[6 Mar 2006 2:08]
Peter Gulutzan
[6 Mar 2006 11:20]
MySQL Verification Team
Thank you for the bug report. mysql> create table tm4 (s1 int) partition by list (s1) (partition p1 values in -> (1)); Query OK, 0 rows affected (0.02 sec) mysql> alter table tm4 rebuild partition p1; Query OK, 0 rows affected (0.02 sec) Records: 0 Duplicates: 0 Warnings: 0 mysql> alter table tm4 rebuild partition; ERROR 2013 (HY000): Lost connection to MySQL server during query
[13 Mar 2006 10:42]
Jon Stephens
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: Verified and documented fix in 5.1.8. Mikael: please add changeset in which this was fixed and mark the bug Closed. Thanks.
[13 Mar 2006 17:15]
Mikael Ronström
Don't know how to get changeset since automatic getting changeset from my commit emails for some reason doesn't work
[16 Mar 2006 8:27]
Jon Stephens
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: Documented bugfix in 5.1.8 changelog. Closed.