MySQL Bugs: #36487: ERROR 2013 (HY000): Lost connection to MySQL server during query

Bug #36487	ERROR 2013 (HY000): Lost connection to MySQL server during query
Submitted:	3 May 2008 12:48	Modified:	6 Jun 2008 20:34
Reporter:	Marian Lander	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	6.0.4	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	ERROR 2013 (HY000): Lost connection to MySQL server during query

Description:
Hi.

I download and compile Mysql-6.0.4-alpha. in a Linux enviroment, I'm running this Mysql server on a 1GB ram, intel core duo  1.60GHz Dell-inspiron Box.

I'm working with falcon tables, and every time I create a new table and want to assign it to a tablespace that doesn't exists this is what happens :

mysql> create table sueldos(id int auto_increment, ganancias decimal(64,3), primary key(id)) engine = falcon tablespace cucu default charset = utf8;
ERROR 2013 (HY000): Lost connection to MySQL server during query
mysql> show tables;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:    1
Current database: primaria

Mysql just disconnect and reconect again, instead of telling me something like 'Tablespace not found' or 'Datafile not found'. After mysql misteriously reconnect back, I want to verify if the table did create.

mysql> show tables;
+--------------------+
| Tables_in_primaria |
+--------------------+
| empleados          |
| sueldos            |
+--------------------+
2 rows in set (0.00 sec)

mysql> describe sueldos;
ERROR 1146 (42S02): Table 'primaria.sueldos' doesn't exist
mysql> drop table sueldos;
Query OK, 0 rows affected (0.00 sec)

I make the same procedure a few times and get the same results. This issue doesn't happend when I assign the table to a tablespace that really exists.

How to repeat:
If you create a table and try to assign it to a tablespace that doesn't exists.

Suggested fix:
instead of mysql server disconnect and reconnect back, it should said a message like 'tablespace not found'.

Thank you for the report.

We can not repeat described behavior with version 6.0.4 on Windows and current development sources on Linux and Mac (version 6.0.6).

Additionally I seen similar crashes on Linux in previous versions, so I think is very likely this bug is fixed.

Please wait next 6.0 release or use BitKeeper mysql-6.0 tree (http://mysql.bkbits.net:8080/mysql-6.0-falcon or http://mysql.bkbits.net:8080/mysql-6.0), test with it in your environment and inform us about results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".