[debian-mysql] Bug#706072: Bug#706072: mysql-server-5.5: Killing a query inside InnoDB causes it to eventually crash with an assertion

[Joshua Dennis]

Is this fix going to get applied to the Debian Wheezy package for mysql? Or is the Debian Wheezy package going to be upgraded to a newer version that includes this fix?

Joshua Dennis
Robertson Heating Supply
IS Manager

On Apr 24, 2013, at 9:15 AM, Norvald H. Ryeng <norvald.ryeng at oracle.com> wrote:

> On Wed, 24 Apr 2013 14:43:14 +0200, Joshua Dennis <jmd at rhsonline.net>
> wrote:
> 
>> Package: mysql-server-5.5
>> Version: 5.5.30+dfsg-1.1
>> Severity: normal
>> 
>> Dear Maintainer,
>> 
>> Yesterday I had a bad situation where mysqld crashed and restarted twice
>> within the span of 20 minutes.  Both times the crash was due to me doing
>> a ctrl-c to stop a subselect query that was taking too long to run.  I
>> found what looks like a similar if not exact bug for this on
>> bugs.mysql.com.  They have it marked as "closed" with no indication as
>> to if there is a fix etc.
>> 
>> http://bugs.mysql.com/bug.php?id=68051
> 
> It is marked as fixed in 5.5.31:
> 
>    "[11 Mar 19:21] Daniel Price
> 
>    Added 5.1.69, 5.5.31, 5.6.11, 5.7.1 changelog.
> 
>    Killing a query caused an InnoDB assertion failure when the same
>    table (cursor) instance was used again. This is the result of a
>    regression error introduced by the fix for Bug#14704286. The fix
>    introduced a check to handle kill signals for long running
>    queries but the cursor was not restored to the proper state."
> 
> Regards,
> 
> Norvald H. Ryeng

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20130424/b6e26f8e/attachment-0001.html>