| Bug #12533 | crash on DESCRIBE <view> after renaming base table column | ||
|---|---|---|---|
| Submitted: | 11 Aug 2005 18:19 | Modified: | 25 Aug 2005 9:53 |
| Reporter: | Matthias Leich | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 5.0 | OS: | |
| Assigned to: | Andrey Hristov | CPU Architecture: | Any |
[12 Aug 2005 12:38]
Andrey Hristov
See the backtrace. The problem is that thd->open_tables is != 0x0 but should be 0x0 therefore somewhere the table t1 is not closed. Breakpoint 1, THD::restore_backup_open_tables_state (this=0x86155a0, backup=0xbfffd140) at sql_class.cc:1832 (gdb) bt #0 THD::restore_backup_open_tables_state (this=0x86155a0, backup=0xbfffd140) at sql_class.cc:1832 #1 0x081c165d in get_all_tables (thd=0x86155a0, tables=0x862adc0, cond=0xbfffd080) at sql_show.cc:2100 #2 0x081c7552 in get_schema_tables_result (join=0x8633130) at sql_show.cc:3690 #3 0x08122cd6 in JOIN::exec (this=0x86320f8) at sql_select.cc:1280 #4 0x08124d28 in mysql_select (thd=0x86155a0, rref_pointer_array=0x86158e8, tables=0x862adc0, wild_num=0, fields=@0xbfffd080, conds=0x0, og_num=0, order=0x0, group=0x0, having=0x0, proc_param=0x0, select_options=2693024256, result=0x862c3b0, unit=0x86155f0, select_lex=0x86157cc) at sql_select.cc:2085 #5 0x08120123 in handle_select (thd=0x86155a0, lex=0x86155e0, result=0x862c3b0, setup_tables_done_option=0) at sql_select.cc:238 #6 0x080eb04e in mysql_execute_command (thd=0x86155a0) at sql_parse.cc:2414 #7 0x080f367f in mysql_parse (thd=0x86155a0, inBuf=0x862a6f8 "DESCRIBE v1", length=11) at sql_parse.cc:5386 #8 0x080e93b7 in dispatch_command (command=COM_QUERY, thd=0x86155a0, packet=0x8617381 "DESCRIBE v1", packet_length=12) at sql_parse.cc:1657 #9 0x080e8c6f in do_command (thd=0x86155a0) at sql_parse.cc:1460 #10 0x080e7e05 in handle_one_connection (arg=0xbfffd080) at sql_parse.cc:1113 #11 0x080d7aac in create_new_thread (thd=0x86155a0) at mysqld.cc:3642 #12 0x080d816b in handle_connections_sockets (arg=0x0) at mysqld.cc:3914 #13 0x080d7530 in main (argc=-1073753984, argv=0xbffff1c4) at mysqld.cc:3313 (gdb)
[12 Aug 2005 14:03]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/28225
[16 Aug 2005 9:59]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/28331
[16 Aug 2005 19:26]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/28349
[17 Aug 2005 9:09]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/28376
[23 Aug 2005 12:11]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/28677
[25 Aug 2005 6:56]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/28803
[25 Aug 2005 7:18]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/28804
[25 Aug 2005 7:24]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/28805
[25 Aug 2005 9:53]
Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
Additional info:
Documented bugfix in 5.0.13 changelog. Closed.
Description: --disable_warnings DROP TABLE IF EXISTS t1; DROP VIEW IF EXISTS v1; --enable_warnings CREATE TABLE t1 (f4 CHAR(5)); CREATE VIEW v1 AS SELECT * FROM t1; DESCRIBE v1; ALTER TABLE t1 CHANGE COLUMN f4 f4x CHAR(5); DESCRIBE v1; -----> 2013: Lost connection to MySQL server during query It looks like this bug was introduced between 9.-11.08.2005. My environment: - Intel PC with Linux(SuSE 9.3) - MySQL compiled from source Version 5.0 ChangeSet@1.1979, 2005-08-11 How to repeat: Please execute the statements above