Gisella, .43 only prints info when there is MySQL server activity. I have changed it to .44 so that it always prints info every 15 seconds, regardless of server activity.
If you want to study locks, then innodb_lock_monitor is the right tool. About your other question, I am afraid that timestamp fields do not help you to prevent deadlocks. The trick in preventing deadlocks is accessing the tables and rows in a predefined order in your transactions, in very difficult cases using LOCK TABLES to all your tables in a transaction. A third trick is to create "semaphore" rows: at the start of a transaction update the "semaphore" row. These updates serialize your transactions, and deadlocks are prevented. Regards, Heikki http://www.innodb.com/ibman.html >Hello, > >I'm running into the "1000000" 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: >>mysqld-max-nt --standalone > >The server starts. > >Then, I went to another window and created the table innodb_monitor as >mentioned >in the manual as an admin user (that I created). It is created. > > >I do not see any output on the window where I started mysqld-max-nt. > >Will I get an output only if there is a deadlock problem? > >Thanks, > >Gisella > > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
