On Wed, 24 Apr 2013 14:43:14 +0200, Joshua Dennis <j...@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
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
