Re: deleting from an InnoDB table with a composite PK > 500 chars crashes mysqld

hi! > "Heikki" == Heikki Tuuri <[EMAIL PROTECTED]> writes: Heikki> Hi! Heikki> Ok, I found that in unireg.h MAX_KEY_LENGTH is defined as 500, and that is Heikki> used, for example, in the opt_range.cc PARAM struct as the key value buffer Heikki> size. A memory overrun will happen if a key l

Re: deleting from an InnoDB table with a composite PK > 500 chars crashes mysqld

Hi! Ok, I found that in unireg.h MAX_KEY_LENGTH is defined as 500, and that is used, for example, in the opt_range.cc PARAM struct as the key value buffer size. A memory overrun will happen if a key length is > 500 bytes. InnoDB allows keys up 3500 bytes in size. Fix: change MAX_KEY_LENGTH in u

Re: deleting from an InnoDB table with a composite PK > 500 chars crashes mysqld

> Number of processes running now: 0 > 011221 15:03:28 mysqld restarted > InnoDB: Database was not shut down normally. > InnoDB: Starting recovery from log files... > InnoDB: Starting log scan based on checkpoi

deleting from an InnoDB table with a composite PK > 500 chars crashes mysqld

ections >Fix: Shorten PK to <= 500 chars. >Submitter-Id: >Originator: >Organization: CodeIt Computing >MySQL support: [none | licence | email support | extended email support ] >Synopsis: deleting from an InnoDB table with a composite PK > 500 chars crash