Details

    • Task
    • Status: Closed (View Workflow)
    • Trivial
    • Resolution: Duplicate
    • None
    • None
    • None

    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 =)

      Attachments

        Issue Links

          Activity

            serg Sergei Golubchik added a comment - - edited

            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.

            serg Sergei Golubchik added a comment - - edited 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.

            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

            rspadim roberto spadim added a comment - 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

            please close this one, MDEV-4619 is better explained

            rspadim roberto spadim added a comment - please close this one, MDEV-4619 is better explained

            People

              Unassigned Unassigned
              rspadim roberto spadim
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.