[MDEV-296] LOCK INFORMATION Created: 2012-05-25  Updated: 2013-06-05  Resolved: 2013-06-05

Status: Closed
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Trivial
Reporter: roberto spadim Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-4619 PLUGINS - Add LOCKS information at I_... Closed

 Description   

Hi guys,
today i received some information at mysql.dev bugs,
http://bugs.mysql.com/bug.php?id=61261

it´s about innodb lock table information:
http://dev.mysql.com/doc/refman/5.5/en/innodb-locks-table.html

since mysql is less opensource friendly, and i don´t think they will implement more feature soon,
could we add a 'SHOW LOCK' in mariadb? i don´t know if locks are engine based or database based, but could be very nice to have a wait to get locks informations where a database get locked and dba/users want know why it was locked

thanks =)

 Comments   
Comment by Sergei Golubchik [ 2012-05-27 ]

There are locks on different levels. Engine internal locks (like row locks) and locks in the sql layer, placed by the mariadb.
the server can only show locks that it knows about. it can show table level locks and metadata locks, but not row- or page-level locks.

Comment by roberto spadim [ 2012-08-30 ]

could it 'ask' to engine and engine return in a standard method the locks?
for example

type = field,row,partition,page,table,others,no information from engine
values = long text with human engine information

Comment by roberto spadim [ 2013-06-05 ]

please close this one, MDEV-4619 is better explained

Generated at Thu Feb 08 06:27:41 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.