Hi!
HeikkiiH == Heikki Tuuri [EMAIL PROTECTED] writes:
HeikkiiH Ken,
HeikkiiH the 'connection lost' error suggests some bug in the client or
HeikkiiH communication. Since you are running 4.0.1-alpha, it could be something with
HeikkiiH the query cache. I think Sanja has already fixed some
Hi!
Heikki == Heikki Tuuri [EMAIL PROTECTED] writes:
Heikki Sanja,
Heikki maybe adding some debug code to the client or the server would help? After
Heikki all, the symptom is easy to notice: the client claims the connection to the
Heikki server is broken. Why does it claim that?
This could
Hi Monty!
I am combining two messages into one:
Heikki server is broken. Why does it claim that?
This could happen if some client code set the 'thd-killed' flag.
The main problem here is why we should get this in mysqldump, but
not
in 'mysql'.
Ken, did you get any output from mysqldump
Hi!
On Mon, Jan 21, 2002 at 05:06:41PM -0500, Ken Menzel wrote:
Hi Heikki and All,
Yes, it seems to be a cache problem, it happens to both MyISAM
I can't reproduce this bug.
Can you create test-suit to reproduce this bug and download it to
ftp://support.mysql.com/pub/mysql/secret ?
PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Tuesday, January 22, 2002 3:47 AM
Subject: Re: mysql cache err with mysqldump? was: Innodb funny error
Hi!
On Mon, Jan 21, 2002 at 05:06:41PM -0500, Ken Menzel wrote:
Hi Heikki and All,
Yes, it seems to be a cache problem
Byelkin [EMAIL PROTECTED]
Cc: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED]
[EMAIL PROTECTED]; [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Tuesday, January 22, 2002 4:28 PM
Subject: Re: mysql cache err with mysqldump? was: Innodb funny error
Hi Alexander,
I am not sure I can create a test-suite
All,
Tuesday, January 22, 2002, 12:06:41 AM, you wrote:
KMYes, it seems to be a cache problem,
[]
KM Also it only seems to affect mysqldump!
BTW, once it helped me to solve such a very-very similar problem
by only adding -q to the mysqldump commandline. God knows why was all the
19 small
rows!
--opt is your friend :)
Ken
- Original Message -
From: Egor Egorov [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 22, 2002 10:36 AM
Subject: mysql cache err with mysqldump? was: Innodb funny error
All,
Tuesday, January 22, 2002, 12:06:41 AM, you wrote
: Re: Innodb funny error
Ken,
the 'connection lost' error suggests some bug in the client or
communication. Since you are running 4.0.1-alpha, it could be
something with
the query cache. I think Sanja has already fixed some bugs there
since 4.0.1
was released. The query cache is suspect since
I've had a similar error when creating innodb tables, using a 4.0.1 client,
and a .47 server, if I loaded my create statement from a text file, the
innodb table wouldn't create. Change the type to myisam and it worked fine.
If I wound up creating it line by line, it worked fine. This might
Hi Heikki,
Thought you might want to hear this one, I was trying to mysqldump
our support database (all tables innodb) WHen I got the following
error:
bash-2.04$ mysqldump --opt -uken -p supportdb terms supportdb.dump
Enter password:
mysqldump: Error 2013: Lost connection to MySQL server
Ken,
the 'connection lost' error suggests some bug in the client or
communication. Since you are running 4.0.1-alpha, it could be something with
the query cache. I think Sanja has already fixed some bugs there since 4.0.1
was released. The query cache is suspect since the error did not crash the
12 matches
Mail list logo
