Percona Server moved to https://jira.percona.com/projects/PS

Add option to switch to "old" get_lock() behavior

  1. Series 5.6
  2. Bug #1401528
Bug #1401528 reported by Valerii Kravchuk
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Invalid
Undecided
Unassigned
5.5
Invalid
Undecided
Unassigned
5.6
Triaged
High
Unassigned
5.7
Invalid
Undecided
Unassigned

Bug Description

Percona Server 5.6.19-67.0 added new feature, "Multiple user level locks per connection", see http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.19-67.0.html. It changes behavior of get_lock()/release_lock() functions notably in the middle of 5.6 GA life cycle, may break existing applications that rely on old behavior of get_lock() (it releases/replaces lock with the same name previously got in the same connection) and we still miss release_all_locks() function (we have bug #1396336 that requests to implement missing RELEASE_ALL_LOCKS()).

It would be nice to have an option to get old get_lock() behavior (if set at server startup). Please, implement it.

Valerii Kravchuk (valerii-kravchuk)
tags: added: i48942
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

We also have bug 1396336, which is a different feature request to achieve the same goal.

Laurynas Biveinis (laurynas-biveinis)
tags: added: get-lock
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-3241

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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