Bug #38816 | kill + flush tables with read lock + stored procedures causes crashes! | ||
---|---|---|---|
Submitted: | 15 Aug 2008 7:42 | Modified: | 7 Aug 2009 0:35 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S1 (Critical) |
Version: | 5.0.66a, 5.1.22, 5.1.28, 6.0.7 | OS: | Any |
Assigned to: | Gleb Shchepa | CPU Architecture: | Any |
Tags: | flush tables with read lock, KILL |
If the data you need to attach is more than 3MB, you should create
a compressed archive of the data and a README file that describes the data
with a filename that includes the bug number (recommended filename:
mysql-bug-data-38816.zip
) and upload one to sftp.oracle.com.
A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com)
and a client that supports SFTP are required in order to access the SFTP server.
To upload the file to sftp.oracle.com:
- Open an SFTP client and connect to
sftp.oracle.com
. Specify port2021
and remote directory/support/incoming/
. - Log in with your newly created Oracle Web account (email address) and password.
- Upload the archive to
/support/incoming
. - Once you have uploaded the file, add a comment to this bug to notify us about it.
sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming
Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.
testcase. run against server and wait for crash, or check valgrind errors!
Attachment: bug38816.c (text/plain), 7.77 KiB.