Bug #32782 | User lock hash fails to find lock | ||
---|---|---|---|
Submitted: | 27 Nov 2007 17:57 | Modified: | 7 May 2009 14:27 |
Reporter: | Chuck Bell | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: Backup | Severity: | S3 (Non-critical) |
Version: | 6.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[27 Nov 2007 17:57]
Chuck Bell
[4 Dec 2007 17:48]
Chuck Bell
Corrected status to verified.
[19 Feb 2009 19:01]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/66954 2754 Horst Hunger 2009-02-19 2. fix for bug#39484: I resetted the timeout values of get_lock as they have no influence on the actual bug. Due to bug#32782 I added NULL as value to the release_lock as being successful. I also replaced the first 2 "sleep 1" by wait conditions. the last 2 sleeps have not been replaced as I have not found a proper condition leading to deterministic results. All is described in comments.
[7 May 2009 14:27]
Chuck Bell
The DBUG_SYNC_POINT code is no longer used therefore this bug is a non-issue. The DBUG_SYNC_POINT code was replaced with the (relatively) new DEBUG_SYNC macro in debug_sync.h.