Release table metadata lock for SELECT when ready to fetch the rows

Bug #1440054 reported by Valerii Kravchuk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Won't Fix
Undecided
Unassigned
5.6
Triaged
Wishlist
Unassigned
5.7
Triaged
Wishlist
Unassigned

Bug Description

See this upstream bug report for the details:

http://bugs.mysql.com/bug.php?id=76588

This is essentially a feature request to implement a relaxed metadata locking model for SELECTs (the same as we have for PREPARE maybe?).

Is this possible any time soon?

description: updated
tags: added: i52042 upstream
Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

It seems lock released after we execute PREPARE is then taken again after we executed EXECUTE. So, real question remain:

Is there any way to release metadata lock:

mysql> select * from performance_schema.metadata_locks\G
*************************** 1. row ***************************
          OBJECT_TYPE: TABLE
        OBJECT_SCHEMA: test
          OBJECT_NAME: t
OBJECT_INSTANCE_BEGIN: 140044187351136
            LOCK_TYPE: SHARED_READ
        LOCK_DURATION: TRANSACTION
          LOCK_STATUS: GRANTED
               SOURCE: sql_parse.cc:5585
      OWNER_THREAD_ID: 24
       OWNER_EVENT_ID: 16

(the above is the output from 5.7) as soon as we've determined list of columns (prepared the statement) and then do not set it again, even when autocommit=0?

description: updated
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2462

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.