Why do I keep getting HEAP to MyISAM conversion on my mysql server

Question

We had problems with our MySQL server intermittently. He continues to issue many of these requests at the same time (thus adding them to his list of processes). We use the MyISAM db pool and the connection pool through Glassfish v3 for the Grails application.

db_user myhost: 35143 db Request 39

converting HEAP to MyISAM /* mysql-connector-java-5.1.7 ( Revision: ) */SHOW VARIABLES WHERE Variable_name ='language' OR Variable_name = 'net_write_timeout' OR Variable_name = 'interactive_timeout' OR Variable_name = 'wait_timeout' OR Variable_name = 'character_set_client' OR Variable_name = 'character_set_connection' OR Variable_name = 'character_set' OR Variable_name = 'character_set_server' OR Variable_name = 'tx_isolation' OR Variable_name = 'transaction_isolation' OR Variable_name = 'character_set_results' OR Variable_name = 'timezone' OR Variable_name = 'time_zone' OR Variable_name = 'system_time_zone' OR Variable_name = 'lower_case_table_names' OR Variable_name = 'max_allowed_packet' OR Variable_name = 'net_buffer_length' OR Variable_name = 'sql_mode' OR Variable_name = 'query_cache_type' OR Variable_name = 'query_cache_size' OR Variable_name = 'init_connect'

We assume that GORM (Grails ORM) creates temporary tables that invoke these queries. Why do I keep getting the HEAP to MyISAM conversion on my mysql server?

Answer 1

About the message converting HEAP to MyISAM, the following answer writes:

, , MySQL , . , MySQL MyISAM db ( , ). , , .

- tmp_table_size, , . , LIMIT OFFSET OFFSET, , . , : . TWO , OFFSET-Ted SIX OFFSET. , .

, MySQL (, , MyISAM), Grails. , - .