Bug #36927 | Falcon: crash altering table's tablespace | ||
---|---|---|---|
Submitted: | 23 May 2008 18:21 | Modified: | 23 May 2008 18:41 |
Reporter: | Peter Gulutzan | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S3 (Non-critical) |
Version: | 6.0.6-alpha-debug | OS: | Linux (SUSE 10 | 32-bit) |
Assigned to: | CPU Architecture: | Any |
[23 May 2008 18:21]
Peter Gulutzan
[23 May 2008 18:41]
Peter Gulutzan
Well, this one didn't last long ... Bug#34617 Falcon assertion in StorageHandler::addTable, line 622 also shows a crash with two ALTERS. So this is a duplicate.
[17 Jun 2008 13:04]
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/47997 2707 John H. Embretsen 2008-06-17 Bug#33723 - ALTER TABLE into non-existing Falcon tablespace blocks further ALTERs Expanded test falcon_bug_34617 to include further *valid* ALTER TABLE statement after invalid ALTER TABLE into non-existing tablespace. Also added script header and some comments. Added reference to additional bugs covered by this test, i.e. Bug#33397 - ALTER TABLE into non-existing Falcon tablespace causes vague error. and the duplicate Bug#36927.