Bug #20816 SPATIAL KEY InnoDB crash
Submitted: 2 Jul 2006 22:46 Modified: 3 Jul 2006 8:45
Reporter: Ask Hansen (Basic Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.22 OS:Linux (Linux x86_64)
Assigned to: CPU Architecture:Any

[2 Jul 2006 22:46] Ask Hansen
The test case from bug #15860 still makes the server crash.   I got the impression from that bug that creating the index shouldn't be possible anymore, but it is and it makes the server crash.

Are InnoDB tables just not supported anymore?

060702 15:42:26  InnoDB: Warning: using a partial-field key prefix in search.
InnoDB: index `location_idx` of table `prod/cities`. Last data field length 34 bytes,
InnoDB: key ptr now exceeds key end by 2 bytes.
InnoDB: Key value in the MySQL format:
 len 32; hex 73dbd9c4bf8b42405ad40c3c01b943401708182a3c6d55c0828e0623b96155c0; asc s     B@Z  <  C@   *<mU    # aU ;
060702 15:42:26InnoDB: Assertion failure in thread 1158191424 in file row0sel.c line 2212
InnoDB: Failing assertion: buf <= original_buf + buf_len
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

How to repeat:
See bug #15860.
[2 Jul 2006 22:48] Ask Hansen
In #15860 Alex said:

"This bug was actually fixed as you can't create spatial index in InnoDB table
anymore, so the server doesn't crash in the manner mentioned above."

Hardly a fix, but even that doesn't seem to be working...
[3 Jul 2006 8:45] Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

And as Alexey said, you can not create SPATIAL INDEX using last 5.0.23 bk sources:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 5.0.23
mysql> CREATE TABLE geom (g GEOMETRY not null, SPATIAL INDEX(g)) engine innodb;
ERROR 1464 (HY000): The used table type doesn't support SPATIAL indexes