0

We run several databases where we need to increase the default value of MI_MAX_KEY_LENGTH. This appears to need to be set when the daemon is built. This makes keeping up with the regular security updates a pain, and delays them.

I'm wondering a few things:

  1. Is there a secure/trusted APT repo I could used with pre-built packages with the increased MI_MAX_KEY_LENGTH size?
  2. Is there any way to set MI_MAX_KEY_LENGTH at runtime, instead of needing to build this setting in?
  3. Is there any easy way to safely automate apt updates to make the change to MI_MAX_KEY_LENGTH and build the new package with apt when the unattended updates occur?

I've tried researching, but thus far I have not found a repo with pre-built packages with increased MI_MAX_KEY_LENGTH. I've also tried researching how to set this at runtime or how to automate builds with this change with in apt, so the builds can be made and distributed unattended, but I have had no luck.

I'm hoping I'm not the first person with this issue, and there is already an easy solution out there.

Adam Harrison
  • 1
  • 1
  • 1
    As far as I know, this max key length only applies to MyISAM tables. Are you aware that InnoDB supports up to 3072 bytes for a key length? MyISAM is practically obsolete and all improvements in MySQL are going into InnoDB. Besides that, InnoDB has better performance, MyISAM [doesn't support ACID](https://stackoverflow.com/a/17706717/20860) and it is susceptible to data corruption. I haven't used MyISAM for years. – Bill Karwin Mar 01 '23 at 20:12

0 Answers0