Bug #28112 | delete from table using results from another query fails | ||
---|---|---|---|
Submitted: | 26 Apr 2007 5:57 | Modified: | 3 Jun 2007 12:52 |
Reporter: | Rotem Fogel | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.1.16-beta | OS: | Solaris |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[26 Apr 2007 5:57]
Rotem Fogel
[26 Apr 2007 7:55]
Sveta Smirnova
Thank you for the report. But there is no 5.15 MySQL server. Please indicate accurate version of the server you use. Also please provide output of SHOW CREATE TABLE and SHOW TABLE STATUS for tables MyTab and MyTabDel
[26 Apr 2007 10:31]
Rotem Fogel
CREATE TABLE `mytab` ( `MYID` varchar(255) COLLATE latin1_general_ci NOT NULL, `MYSEG` varchar(255) COLLATE latin1_general_ci DEFAULT NULL, `MYSUB` varchar(255) COLLATE latin1_general_ci DEFAULT NULL, PRIMARY KEY (`MYID`), ) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci CREATE TABLE `mytabdel` ( `MYSUB` varchar(255) COLLATE latin1_general_ci DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci
[2 May 2007 17:27]
Heikki Tuuri
Maybe the same bug as http://bugs.mysql.com/bug.php?id=27276
[3 May 2007 0:37]
MySQL Verification Team
Rotem, Please paste the exact query that causes a crash, and the full output of SHOW CREATE TABLE <tablename> for each involved table. You can make it a private comment if needed.
[3 May 2007 12:52]
MySQL Verification Team
Please answer last Shane's question. Thanks in advance.
[3 Jun 2007 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[29 Oct 2008 7:42]
Marko Mäkelä
Bug #27276 could be a bogus warning.
[29 Oct 2008 7:56]
Marko Mäkelä
Did the delete fail? Did CHECK TABLE fail? If no, then this is probably just a duplicate of Bug #27276. I fail to see how the DELETE...SELECT could have prompted InnoDB to contract the insert buffer B-tree, invoking ibuf_get_merge_page_nos() on a dropped *.ibd tablespace, as discussed in Bug #27276. It should be just a coincidence, caused by the master thread or by another thread that was buffering some inserts while the statement was running.