: [EMAIL PROTECTED]
Sent: 12/1/2001 6:35 AM
Subject: RE: mysqldump: problem/question
Weaver, Walt writes:
> I knew it. Nobody bothered to read my post.
>
> The original problem involved running a lightweight version of
mysqldump in
> a simulated nanokernel environment with reduced power re
Weaver, Walt writes:
> I knew it. Nobody bothered to read my post.
>
> The original problem involved running a lightweight version of mysqldump in
> a simulated nanokernel environment with reduced power resources. The
> ultimate result, we hope, is to use it to record Quidditch matches being
> pl
,
--Walt Weaver
Bozeman, Montana, USA
-Original Message-
From: sherzodR
To: Weaver, Walt
Cc: [EMAIL PROTECTED]
Sent: 11/30/2001 3:14 AM
Subject: re: mysqldump: problem/question
So what was the problem?
Weaver, Walt wrote:
WW: Okay, I know you guys have been wracking your brains
So what was the problem?
Weaver, Walt wrote:
WW: Okay, I know you guys have been wracking your brains for the last two days
WW: trying to solve my problem of mysqldump running out of memory while dumping
WW: a large table.
WW:
WW: I figured it out, so you can all go on wi
Okay, I know you guys have been wracking your brains for the last two days
trying to solve my problem of mysqldump running out of memory while dumping
a large table.
I figured it out, so you can all go on with your lives.
My copy of Paul DuBois' MySQL book came today and immediately solved my
pr
Another newbie question:
I'm trying to do a mysqldump of a fairly large, wide (two longblobs) table,
and am running into memory problems.
After running for some time the mysqldump process will die with an "Out of
memory (needed 8164 bytes)" message.
Is there a way to tell mysqldump to not cache
