| Bug #27604 | Update query with Join crashes mysqld | ||
|---|---|---|---|
| Submitted: | 3 Apr 2007 1:29 | Modified: | 11 Jun 2007 6:20 |
| Reporter: | Kristian Ducharme | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S1 (Critical) |
| Version: | 14.12 Distrib 5.0.37, for pc-linux-gnu ( | OS: | Linux (Redhat 9 (Shrike)) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | crash, join, UPDATE | ||
[3 Apr 2007 1:29]
Kristian Ducharme
[3 Apr 2007 1:29]
Kristian Ducharme
mysqld stack trace
Attachment: mysql_stack.rtf (application/rtf, text), 2.68 KiB.
[3 Apr 2007 7:30]
Sveta Smirnova
Thank you for the report. Please provide output of SHOW TABLE STATUS LIKE 'emails_search4more_bl' and SHOW TABLE STATUS LIKE 'emails_search4more_queue'
[3 Apr 2007 16:56]
Kristian Ducharme
show table status like 'emails_search4more_bl' \G;
*************************** 1. row ***************************
Name: emails_search4more_bl
Engine: InnoDB
Version: 10
Row_format: Compact
Rows: 124010
Avg_row_length: 105
Data_length: 13123584
Max_data_length: 0
Index_length: 48988160
Data_free: 0
Auto_increment: 6261033
Create_time: 2007-03-30 18:04:16
Update_time: NULL
Check_time: NULL
Collation: latin1_swedish_ci
Checksum: NULL
Create_options:
Comment: InnoDB free: 5120 kB
show table status like 'emails_search4more_queue' \G;
*************************** 1. row ***************************
Name: emails_search4more_queue
Engine: InnoDB
Version: 10
Row_format: Compact
Rows: 9774
Avg_row_length: 162
Data_length: 1589248
Max_data_length: 0
Index_length: 5079040
Data_free: 0
Auto_increment: 727162
Create_time: 2007-03-30 18:04:25
Update_time: NULL
Check_time: NULL
Collation: latin1_swedish_ci
Checksum: NULL
Create_options:
Comment: InnoDB free: 4096 kB
***Note that emails_search4more_queue varies in length daily, email_search4more_bl does not change as often.
[11 May 2007 6:19]
Sveta Smirnova
Thank you for the report. I can not repeat described behaviour. Please upgrade to current 5.0.41 version and check if problem has solved.
[11 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".
