Bug #6291 mysqld crashes when --skip-innodb and set @@storage_engine=innodb

• Submitted: 27 Oct 2004 19:55
• Modified: 10 May 2005 9:53
• Reporter: Guilhem Bichot
• Status: Can't repeat
• Category: MySQL Server
• Severity: S2 (Serious)
• Version: 4.1
• OS: Linux (Linux)
• Assigned to: Sergei Glukhov
• CPU Architecture: Any

[27 Oct 2004 19:55] Guilhem Bichot

Description:
Noticed that while running:
./mysql-test-run --skip-innodb t/multi_update.test
in 5.0 (in this version, multi_update tests more than in 4.x).
If mysqld started with --skip-X where X is innodb or bdb, and one does
set storage_engine=X;
create table t1 ( c char(8) not null );
show create table t1;
I have seen mysqld get a segfault on one of the two last lines.
4.0 does not seem to have problems.
We would expect the "create" to create a MyISAM table and give a warning, not crash.

How to repeat:
If mysqld started with --skip-X where X is innodb or bdb, and one does
set storage_engine=X;
create table t1 ( c char(8) not null );
show create table t1;

[27 Oct 2004 19:56] Guilhem Bichot

Emphasizing: bug is in *4.1* (and in 5.0). And not in 4.0.

[29 Oct 2004 12:34] Sergei Glukhov

ChangeSet
  1.2063 04/10/29
  Fix for bug #6291: mysqld crashes when --skip-innodb and set @@storage_engine=innodb

[10 May 2005 9:53] Sergei Glukhov

Checked on latest 4.1 tree. Can't repeat