Thank you for taking the time to report this bug and helping to make
Ubuntu better. The version of Ubuntu you're reporting this issue on is
in End of Life status, and newer versions have fixed this issue. You can
learn more about this at https://wiki.ubuntu.com/Releases
** Changed in:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The version of Ubuntu you're reporting this issue on is
in End of Life status, and newer versions have fixed this issue. You can
learn more about this at https://wiki.ubuntu.com/Releases
** Changed in:
Reopening
** Changed in: mysql-dfsg-5.0 (Ubuntu Dapper)
Status: Invalid = Incomplete
--
'flush tables with read lock' causes mysql server to deadlock
https://bugs.launchpad.net/bugs/105225
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
[Expired for mysql-dfsg-5.0 (Ubuntu Dapper) because there has been no
activity for 60 days.]
--
'flush tables with read lock' causes mysql server to deadlock
https://bugs.launchpad.net/bugs/105225
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Needs reproduction recipe, so it's not 'triaged'.
** Changed in: mysql-dfsg-5.0 (Ubuntu Dapper)
Status: Triaged = Incomplete
--
'flush tables with read lock' causes mysql server to deadlock
https://bugs.launchpad.net/bugs/105225
You received this bug notification because you are a member
On Tue, Jul 17, 2007 at 01:34:48PM -, Scott Kitterman wrote:
Here is the svn commit that fixed the problem:
http://lists.mysql.com/commits/6835
Someon who is more familiar that me (e.g. more than not at all) with the
mysql code base should look this over and pull the relevant bits out
Can someone provide an easy way to reproduce this bug? I took a cleanly
installed mysql-server-5.0 instance, created a database, created a table
and dumped a stack of data into it, ran 'FLUSH TABLES WITH READ LOCK',
but no luck.
--
Soren Hansen
Ubuntu Server Team
http://www.ubuntu.com/
--
okay, so where do things go from here? do you have to make the changes for it
to be considered for SRU, or do I? it looks
like whoever is producing the gutsy one is?
--
'flush tables with read lock' causes mysql server to deadlock
https://bugs.launchpad.net/bugs/105225
You received this bug
Here is the svn commit that fixed the problem:
http://lists.mysql.com/commits/6835
Someon who is more familiar that me (e.g. more than not at all) with the
mysql code base should look this over and pull the relevant bits out for
this bug (the commit fixed two bugs). It should be easy enough to
Thanks taking the time to report this bug and helping to make Ubuntu
better. However, I am closing it because the bug has been fixed in the
latest development version of Ubuntu - the Gutsy Gibbon.
If you need a fix for the bug in previous versions of Ubuntu, please
follow the instructions for How
Please don't suggest Backports for bug fixes. Backports are for new
features. Since *-backports are not enabled by default, bugs needing to be
in released versions should be addressed through the SRU process. That way
all Ubuntu users can benifit.
--
'flush tables with read lock' causes
So where is the LTS for dapper? or is that only for some security updates?
5.0.22 of mysql is going to be pretty obsolete by the
time dapper has finished being supported in 2011. Or do we only get support if
we pay for it or are willing to use backports?
--
'flush tables with read lock' causes
I've reopen the bug for dapper.
This bug may qualify for a SRU, which is described here:
https://wiki.ubuntu.com/StableReleaseUpdates.
** Changed in: mysql-dfsg-5.0 (Ubuntu Dapper)
Importance: Undecided = Medium
Status: New = Triaged
--
'flush tables with read lock' causes mysql
13 matches
Mail list logo
