Bug #989 If DROP TABLE while there's an active transaction, wrong binlog order
Submitted: 4 Aug 2003 3:16 Modified: 14 Apr 18:42
Reporter: Guilhem Bichot
Status: Closed
Category:Server: Locking Severity:S1 (Critical)
Version:4.0 and higher OS:Any (all)
Assigned to: Davi Arnaut Target Version:6.0-beta
Tags: bfsm_2007_06_28, falcon, bfsm_2007_06_21
Triage: Triaged: D2 (Serious) / R4 (High) / E5 (Major)

File: Maximum allowed size is 500KB.
Description:
Privacy:

If the data you need to attach is more than 500KB, 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 (example: bug-data-989.zip), and use FTP to upload the archive to ftp://ftp.mysql.com/pub/mysql/upload/. Once you have uploaded the file, add a comment to this bug to notify us about it. Note: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it.

All entries become the exclusive editorial property of Sun Microsystems, Inc.

[4 Aug 2003 3:17] Guilhem Bichot
a test file for the testsuite, which reproduces the bug

Attachment: innodb_drop.test (application/octet-stream, text), 504 bytes.