Bug #25673 spatial index corruption, error 126 incorrect key file for table
Submitted: 17 Jan 2007 9:27 Modified: 15 Mar 2007 2:46
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: MyISAM storage engine Severity:S1 (Critical)
Version:5.0.34,5.0.36-BK,5.1.15-BK OS: *
Assigned to: Ingo Strüwing CPU Architecture:Any
Tags: bfsm_2007_02_01, corruption, myisam, spatial

File: Maximum allowed size is 50MB.

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[17 Jan 2007 9:29] Shane Bester
see top of file for build instructions, host, user, port, etc

Attachment: testcase.c (text/plain), 5.75 KiB.

[24 Feb 2007 11:34] Shane Bester
and here's the promised testcase. simply import using command line client

Attachment: bug25673.zip (application/zip, text), 207.97 KiB.

[25 Feb 2007 5:05] Shane Bester
a final version of testcase, 538 lines long!!!

Attachment: bug25673_reduced.sql (application/octet-stream, text), 54.33 KiB.

[25 Feb 2007 5:53] Shane Bester
same testcase as bug25673_reduced.sql except multirow insert and less indexes are used.

Attachment: bug25673_tiny.sql (application/octet-stream, text), 34.54 KiB.

[2 Mar 2007 21:47] Ingo Strüwing
Some comments on rtree index structures and algorithmns.

Attachment: rtree-indexes.txt (text/plain), 6.42 KiB.