Bug #14575 | MySQL server crashes if you try to access to InnoDB table | ||
---|---|---|---|
Submitted: | 2 Nov 2005 15:18 | Modified: | 16 Mar 2006 15:16 |
Reporter: | Victoria Reznichenko | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0 | OS: | Linux (Linux, Windows) |
Assigned to: | Antony Curtis | CPU Architecture: | Any |
[2 Nov 2005 15:18]
Victoria Reznichenko
[14 Mar 2006 8:57]
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/3809
[16 Mar 2006 8:15]
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/3873
[16 Mar 2006 9:27]
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: Pushed to 5.0.20 repository
[16 Mar 2006 15:16]
Paul DuBois
Noted in 5.0.20 changelog. Attempting to access an <literal>InnoDB</literal> table after starting the server with <option>--skip-innodb</option> caused a server crash. (Bug #14575)