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

Bug #1401528 reported by Valerii Kravchuk on 2014-12-11
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona Server
Status tracked in 5.7
5.1
Undecided
Unassigned
5.5
Undecided
Unassigned
5.6
High
Unassigned
5.7
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.

tags: added: i48942

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

tags: added: get-lock
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers