Bug #58619 killing a long explain query asserts: Assertion `table->key_read == 0' failed.

• Submitted: 1 Dec 2010 5:17
• Modified: 1 Dec 2010 8:25
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Duplicate
• Category: MySQL Server: Optimizer
• Severity: S2 (Serious)
• Version: 5.5.9-debug
• OS: Any
• CPU Architecture: Any
• Tags: explain extended, KILL

[1 Dec 2010 5:17] Shane Bester

Description:
5.5.9-debug:
mysqld: ./sql/sql_base.cc:1513: bool close_thread_table(THD*, TABLE**): Assertion `table->key_read == 0' failed.

Process terminating with default action of signal 6 (SIGABRT)
at: raise (raise.c:64)
by: abort (abort.c:92)
by: __assert_fail (assert.c:81)
by: close_thread_table (sql_base.cc:1513)
by: close_open_tables (sql_base.cc:1293)
by: close_thread_tables (sql_base.cc:1500)
by: open_and_lock_tables (sql_base.cc:5421)
by: open_and_lock_tables (sql_base.h:475)
by: execute_sqlcom_select (sql_parse.cc:4417)
by: mysql_execute_command(THD*) (sql_parse.cc:2046)
by: mysql_parse (sql_parse.cc:5496)
by: dispatch_command (sql_parse.cc:1032)
by: do_command (sql_parse.cc:772)
by: do_handle_one_connection (sql_connect.cc:745)
by: handle_one_connection (sql_connect.cc:684)
by: start_thread (pthread_create.c:301)

only affects debug binary.  this is annoying because killing of long running explains is required for tests to continue without hanging.

How to repeat:
no simple testcase yet. run explain extended on large joins with views and many tables [same as bug 58618 and bug 58604] then kill the query.

[1 Dec 2010 8:25] MySQL Verification Team

debug build asserts like this.
release build dies, same as bug 58604
marking as a duplicate since the testcase is the same.