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
Hi Heikki and All,
Yes, it seems to be a cache problem, it happens to both MyISAM
and innodb table types but simply updating one row in the table maks
the error go away. The table names also seems to change (supporting
the cache idea) and it seems to be mostly readonly tables. Also it
only
