diff options
| author | unknown <svoj@mysql.com/april.(none)> | 2007-07-13 03:25:27 +0500 |
|---|---|---|
| committer | unknown <svoj@mysql.com/april.(none)> | 2007-07-13 03:25:27 +0500 |
| commit | 62738bf97e7a653030361f0dcedf0f4a5c97388d (patch) | |
| tree | 8b756f4a33c9a0e00ed02b2c4753aab9d9b2879f /mysql-test/t/fulltext3.test | |
| parent | 847d6ed75bf396eeccef04205822c6314ff55065 (diff) | |
| download | mariadb-git-62738bf97e7a653030361f0dcedf0f4a5c97388d.tar.gz | |
BUG#29445 - match ... against () never returns
Part 2:
Searching fulltext index for a word with boolean mode truncation
operator may cause infinite loop.
The problem was that "smarter index merge" was used with "trunc-words",
which must never happen.
Affects 5.1 only.
mysql-test/r/fulltext.result:
Addition to a test case for BUG#29445.
mysql-test/t/fulltext.test:
Addition to a test case for BUG#29445.
storage/myisam/ft_boolean_search.c:
Fulltext "smarter index merge" optimization assumes that rows
it gets are ordered by doc_id. That is not the case when we
search for a word with truncation operator. It may return
rows in random order. Thus we may not use "smarter index merge"
optimization with "trunc-words".
Also fixed compiler warning introduced by Part 1 patch.
Diffstat (limited to 'mysql-test/t/fulltext3.test')
0 files changed, 0 insertions, 0 deletions