Heikki,
thanks for the reply. Regarding the trace output, My test has been
bombarding the db server with 15 simultaneous clients, each
generating up to 1000 transaction sets.
I still do not get any output from Innodb Monitor.
I created table innodb_monitor in the database that I'm accessing.
Heikki,
I looked at the mysql error log and all the stuff was there.
I was expecting it on the standard output as the documentation said.
Thanks again. I'll have to restart the server again since the
innodb monitor output on the error log says that I'm not running a debugable
version, so there
Miguel,
I can look at the file /mysql/data/mysql.err by using emacs. I do not need
to stop the server. If I try a Windows tool like WordPad?, yes,
it does not let me see the file.
Heikki,
I checked the task manager. I only have one mysqld running
which is the mysqld-max-nt. I had mysqlgui
PROTECTED]]
Sent: Wednesday, October 31, 2001 1:15 PM
To: Heikki Tuuri; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Gisella Saavedra
Subject: Re: deadlock - Innodb Monitor
At 22:52 31/10/2001 +0200, Heikki Tuuri wrote:
Heikki,
For you to have at the shell prompt the output is necessary
the command
generate secondary indexes?
Regards,
Gisella
-Original Message-
From: Miguel Angel Solórzano [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 2:38 PM
To: Gisella Saavedra; [EMAIL PROTECTED]
Cc: Miguel Angel Solórzano
Subject: RE: deadlock - Innodb Monitor
At 13:50 31/10/2001
Hello,
I'm running into the 100 deadlock error, so I would like to trace the
problem.
Server: mysqld-max-nt 3.23.43
myodbc 2.50.39
Server application that connects to mysqld is multithreaded.
Mysqld has been installed as a service.
I stopped it. Then I issued the following command:
I'm curious. Will adding a timestamp field into various tables
that may cause deadlock, prevent the deadlock from happening?
Thanks,
Gisella
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
