MySQL Manual
A Problems and Common Errors
- A.2 Common Errors When Using MySQL
- A.2.1
Access deniedError - A.2.2
MySQL server has gone awayError - A.2.3
Can't connect to [local] MySQL serverError - A.2.4
Client does not support authentication protocolerror - A.2.5
Host '...' is blockedError - A.2.6
Too many connectionsError - A.2.7
Some non-transactional changed tables couldn't be rolled backError - A.2.8
Out of memoryError - A.2.9
Packet too largeError - A.2.10 Communication Errors / Aborted Connection
- A.2.11
The table is fullError - A.2.12
Can't create/write to fileError - A.2.13
Commands out of syncError in Client - A.2.14
Ignoring userError - A.2.15
Table 'xxx' doesn't existError - A.2.16
Can't initialize character set xxxerror - A.2.17 File Not Found
- A.2.1
A.2.8 Out of memory Error
If you issue a query and get something like the following error:
mysql: Out of memory at line 42, 'malloc.c' mysql: needed 8136 byte (8k), memory in use: 12481367 bytes (12189k) ERROR 2008: MySQL client ran out of memory
note that the error refers to the MySQL client mysql. The
reason for this error is simply that the client does not have enough memory to
store the whole result.
To remedy the problem, first check that your query is correct. Is it
reasonable that it should return so many rows? If so,
you can use mysql --quick, which uses mysql_use_result()
to retrieve the result set. This places less of a load on the client (but
more on the server).
