Bug #4536 InnoDB Monitor doesn't show lock information
Submitted: 13 Jul 2004 11:24 Modified: 13 Jul 2004 11:48
Reporter: Marat Latypov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:4.0.20 OS:Linux (Red Hat 9.0)
Assigned to: CPU Architecture:Any

[13 Jul 2004 11:24] Marat Latypov
Description:
InnoDB Monitor doesn't show lock information in 4.0.20.
But it worked well in 4.0.18

How to repeat:
mysql> drop table if exists innodb_lock_monitor;
Query OK, 0 rows affected (0.00 sec)

mysql>show innodb status;

=====================================
040713 13:15:29 INNODB MONITOR OUTPUT
=====================================
Per second averages calculated from the last 0 seconds

.................................................

------------
TRANSACTIONS
------------
Trx id counter 0 19509988
Purge done for trx's n:o < 0 19509828 undo n:o < 0 0
Total number of lock structs in row lock hash table 6
LIST OF TRANSACTIONS FOR EACH SESSION:

...............................................

---TRANSACTION 0 19509366, not started, process no 28888, OS thread id 196621
MySQL thread id 3, query id 93212 Oleg 10.10.10.16 stn
---TRANSACTION 0 19509986, ACTIVE 4 sec, process no 29036, OS thread id 966668
5 lock struct(s), heap size 320
MySQL thread id 50, query id 93346 Saria 10.10.10.4 stn
---TRANSACTION 0 19509653, ACTIVE 498 sec, process no 29257, OS thread id 1622032
4 lock struct(s), heap size 320
MySQL thread id 90, query id 93069 Galvanik 10.10.10.26 stn
---TRANSACTION 0 19509342, ACTIVE 1417 sec, process no 29151, OS thread id 1409046
6 lock struct(s), heap size 1024, undo log entries 1
MySQL thread id 77, query id 93174 Manager2 10.10.10.6 stn
--------
FILE I/O
--------
................................................

----------------------------
END OF INNODB MONITOR OUTPUT
============================
 
1 row in set (0.02 sec)

mysql> create table innodb_lock_monitor(a INT) ENGINE=InnoDB;
Query OK, 0 rows affected (0.02 sec)

mysql>show innodb status;

=====================================
040713 13:21:11 INNODB MONITOR OUTPUT
=====================================
Per second averages calculated from the last 4 seconds
.....................................

------------
TRANSACTIONS
------------
Trx id counter 0 19510206
Purge done for trx's n:o < 0 19510190 undo n:o < 0 0
Total number of lock structs in row lock hash table 8
LIST OF TRANSACTIONS FOR EACH SESSION:
---TRANSACTION 0 0, not started, process no 29262, OS thread id 1654798
MySQL thread id 92, query id 95072 localhost root
show innodb status
.........................................

---TRANSACTION 0 19509366, not started, process no 28888, OS thread id 196621
MySQL thread id 3, query id 94978 Oleg 10.10.10.16 stn
---TRANSACTION 0 19510205, ACTIVE 0 sec, process no 29036, OS thread id 966668
5 lock struct(s), heap size 320
MySQL thread id 50, query id 95071 Saria 10.10.10.4 stn
---TRANSACTION 0 19510192, ACTIVE 28 sec, process no 29267, OS thread id 1671185
4 lock struct(s), heap size 320
MySQL thread id 93, query id 94999 sklad 10.10.10.22 stn
---TRANSACTION 0 19509653, ACTIVE 840 sec, process no 29257, OS thread id 1622032
4 lock struct(s), heap size 320
MySQL thread id 90, query id 94781 Galvanik 10.10.10.26 stn
---TRANSACTION 0 19509342, ACTIVE 1759 sec, process no 29151, OS thread id 1409046
6 lock struct(s), heap size 1024, undo log entries 1
MySQL thread id 77, query id 94931 Manager2 10.10.10.6 stn
--------
FILE I/O
--------
...........................................

----------------------------
END OF INNODB MONITOR OUTPUT
============================
[13 Jul 2004 11:48] Marko Mäkelä
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

The monitor table names lost their special meaning in 4.0.19 and 4.0.20. The bug has been fixed in 4.1.3 and will be fixed in 4.0.21.