Bug #899 | 32 keys maximum w/ a table | ||
---|---|---|---|
Submitted: | 23 Jul 2003 10:35 | Modified: | 27 Aug 2003 13:14 |
Reporter: | Matthias Urlichs | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S4 (Feature request) |
Version: | all | OS: | Any (all) |
Assigned to: | Igor Babaev | CPU Architecture: | Any |
[23 Jul 2003 10:35]
Matthias Urlichs
[7 Aug 2003 1:02]
Lenz Grimmer
Heikki, is this something you can fix in InnoDB? Or does it need to be fixed in the mysql code instead?
[7 Aug 2003 1:15]
Heikki Tuuri
Lenz, Igor, do not assign this feature request to me :). InnoDB supports 4 billion indexes in a table. The restriction comes from the MySQL optimizer where a 32-bit integer is used as a 'set' type (== bitmap) to describe a set of indexes. Increasing the limit to 64 is relatively straightforward: make that integer longlong. I have now assigned this feature request to Igor Babaev, who is responsible for the SQL optimizer. Regards, Heikki
[7 Aug 2003 1:24]
Matthias Urlichs
A quick grep finds: include/myisam.h:#define MI_MAX_KEY 32 /* Max allowed keys */ sql/unireg.h:#define MAX_KEY 32 /* Max used keys */
[27 Aug 2003 13:14]
Peter Zaitsev
Matthias, Thank you for your feedback, This item is already in MySQL ToDo list and we'll fix this limitation in one of the next MySQL releases.
[20 Oct 2005 9:26]
Saleh Hamad
It will be better if the maximum number of inexes became configurable in my.ini