alter table engine=memory ERROR 1114
In this Document
|
|
Symptoms |
|
|
Cause |
|
|
Solution |
|
|
References |
APPLIES TO:
MySQL Server - Version 5.6 and laterInformation in this document applies to any platform.
SYMPTOMS
When creating, modifying or altering the table engine to MEMORY, you get this error even if max_heap_table_size can host the data:
CAUSE
The MEMORY engine can allocate more memory than its InnoDB or MyISAM equivalent.
If the problematic table contains long varchar, the MEMORY engine will allocate fixed length strings so it can take a lot of space in memory, even more when the utf8 or utf8mb4 character set is used.
SOLUTION
Increase max_heap_table to an even larger value.
Consider using InnoDB with a large buffer pool, so that in practice, the data is in memory and can be accessed concurrently unlike MEMORY table data. There is very little reason to use the MEMORY engine nowadays.
REFERENCES
http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_max_heap_table_sizehttp://dev.mysql.com/doc/refman/5.6/en/memory-storage-engine.html
QQ 273002188 欢迎一起学习
QQ 群 236941212
oracle,mysql,PG 相互交流
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/25099483/viewspace-2113514/ ，如需转载，请注明出处，否则将追究法律责任。
