Bug #36169 create innodb compressed table with too large row size crashed
Submitted: 17 Apr 2008 9:22 Modified: 12 Mar 22:56
Reporter: Shane Bester
Status: Closed
Category:Server: InnoDB Severity:S1 (Critical)
Version:innodb_plugin-1.0.0, standard innodb in 5.1 OS:Any
Assigned to: Timothy Smith Target Version:5.1+
Triage: Triaged: D1 (Critical)

File: Maximum allowed size is 500KB.
Description:
Privacy:

If the data you need to attach is more than 500KB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (example: bug-data-36169.zip), and use FTP to upload the archive to ftp://ftp.mysql.com/pub/mysql/upload/. Once you have uploaded the file, add a comment to this bug to notify us about it. Note: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it.

All entries become the exclusive editorial property of Sun Microsystems, Inc.

[17 Apr 2008 9:23] Shane Bester 
full stack in file to avoid untidy wrapping.

Attachment: bug36169_stack_trace.txt (text/plain), 2.00 KiB.
[17 Apr 2008 9:47] Shane Bester 
10 tables to import.  create table table6 causes a crash..

Attachment: bug36169.sql (application/unknown, text), 35.66 KiB.