List:Internals« Previous MessageNext Message »
From:Stewart Smith Date:May 6 2014 3:28pm
Subject:Re: Incorrect locking for global_query_id
View as plain text  
Tor Didriksen <tor.didriksen@stripped> writes:
>>      mysql_mutex_lock(&LOCK_thread_count);
>>      q= global_query_id;
>>      mysql_mutex_unlock(&LOCK_thread_count);
>> Which is incorrect.
> This goes all the way back to 5.0, when it was in fact correct.
> That mutex was used to protect all sorts of things, including 
> global_query_id.

Yeah, I have some dim horrific memories of that :)

>> It should at least by a my_atomic_load64 with the appropriate lock
>> things around it.
> Which is what we do in 5.7

yay! I hadn't actually checked :)

Incorrect locking for global_query_idStewart Smith5 May
  • Re: Incorrect locking for global_query_idTor Didriksen6 May
    • Re: Incorrect locking for global_query_idStewart Smith6 May
  • Re: Incorrect locking for global_query_idDmitry Lenev6 May
    • Re: Incorrect locking for global_query_idStewart Smith6 May