Bug #8257 | Record-file crash or full mysql crash while joining with a fulltext table | ||
---|---|---|---|
Submitted: | 2 Feb 2005 9:13 | Modified: | 5 Feb 2005 16:49 |
Reporter: | André Bieleman | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S1 (Critical) |
Version: | 4.1.8-Max | OS: | Linux (Fedora Core 1 & Redhat 7.2) |
Assigned to: | CPU Architecture: | Any |
[2 Feb 2005 9:13]
André Bieleman
[2 Feb 2005 9:25]
André Bieleman
Forgot to explicit mention that when not using the boolean mode or when no range lookup is performed the query goes well: mysql> SELECT nf.id FROM k, nf WHERE keyword IN('aa','bb') AND nf.id = k.id AND MATCH (nf.name,nf.alias) AGAINST ('+aa +bb' IN BOOLEAN MODE); ERROR 2013 (HY000): Lost connection to MySQL server during query mysql> SELECT nf.id FROM k, nf WHERE keyword IN('aa') AND nf.id = k.id AND MATCH (nf.name,nf.alias) AGAINST ('+aa +bb' IN BOOLEAN MODE); ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect... Connection id: 11 Current database: debug Empty set (0.01 sec) mysql> SELECT nf.id FROM k, nf WHERE keyword IN('aa','bb') AND nf.id = k.id AND MATCH (nf.name,nf.alias) AGAINST ('aa bb'); +---------+ | id | +---------+ | 313762 | | 464294 | | 496765 | | 565624 | | 1024669 | | 178280 | | 979481 | +---------+ 7 rows in set (1.38 sec) We also have ft_min_word_len = 2 and a custom stopword list.
[5 Feb 2005 16:49]
Jorge del Conde
Hi! I was unable to reproduce this behaviour. By the error messages that you received, it looks like your tables have become corrupted, and unless you provide us with a test-case that reproduces this behaviour, there isn't much we can do. Can you please give us a test-case that re-creates this scenario ? Thanks !
[21 Feb 2005 9:04]
André Bieleman
Tables where certainly not corrupted, because I made new tables like the old ones (CREATE TABLE LIKE) and inserted the data with a INSERT INTO ... SELECT. A random filled table k with 4,4 million records joined with the nf table did also crash the server. I still can't repeat with a random filled fulltext table (nf). But, I'm very pleased to see that the problem is fixed in 4.1.10!! Looks like fix: 'Fixed a crash in a boolean full-text search in certain joins. (Bug #8234)' did it.