At 2:25 PM -0400 5/5/1999, Vivek Khera wrote:
>>>>>> "g" == glen <glen@stripped> writes:
>>> >
>>> > mysqldump: Out of memory (Needed 8164 bytes)
>>> > mysqldump: Got error: 2008: MySQL client run out of memory
>
>g> no the problem is that CLIENT runs out of memory, that is mysqldump in this
>g> case
>g> i don't get it why mysqldump needs so much memory, there's no sorting or
>g> whatsover
>
>You may wish to investigate the "--quick" option to mysqldump.
Specifically, the problem is that mysqldump by default uses
mysql_store_result(), which reads the *entire* result set to the
client all at once. With a huge table, you can see the problem.
With --quick, mysqldump uses mysql_use_result(), which reads rows
from the server a row at a time.
Just don't type ^Z while you're in the middle of dumping your
table.
--
Paul DuBois, paul@stripped
Northern League Chronicles: http://www.snake.net/nl/
