List:General Discussion« Previous MessageNext Message »
From:Vivek Khera Date:May 5 1999 6:25pm
Subject:Re: mysqldump problem
View as plain text  
>>>>> "g" == glen  <glen@stripped> writes:

g> Fraser MacKenzie wrote:
>> Use --big-tables whhen you startup mysqld
>> Fraser
>> On Wed, 5 May 1999, glen wrote:
>> > i have database table which filesize is 550mb and around 5000000 records
>> >
>> > and free system memory about 400mb, including swap space.
>> > when trying to mysqldump that table then mysqldump fails with error

I've said it before and I'll say it again: just because your system
has these resources does not mean your process can use all of them.
Unix is a multi-user system, and must share the resources. Be sure
your process is allowed to use the resources you're expected it to get.

>> >
>> > 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.


Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@stripped       Rockville, MD       +1-301-545-6996
PGP & MIME spoken here  
mysqldump problemglen5 May
  • Re: mysqldump problemFraser MacKenzie5 May
    • Re: mysqldump problemglen5 May
      • Re: mysqldump problemVivek Khera5 May
        • Re: mysqldump problemPaul DuBois5 May
    • Problem with mysqlimport under dec-osfFabrice Marchal5 May
      • Problem with mysqlimport under dec-osfJani Tolonen11 May
    • Re: mysqldump problemChristian Mack5 May