Victor Pendleton wrote:
What does the explain plan look like? It sounds like the query is using the
fulltext index. Remember that only one index per table can be used when
performing a query.
explain select id, headline, date_format(s.post_date,'%Y/%m/%d') directory, post_date sort_date
from story s where type=3 and status=9
and post_date > date_sub(now(),interval 80 day)
and match(headline,deck) against ('halo')
order by post_date desc limit 3
+-------+----------+---------------------------+--------+---------+--------+------+-----------------------------+
| table | type | possible_keys | key | key_len | ref | rows | Extra |
+-------+----------+---------------------------+--------+---------+--------+------+-----------------------------+
| s | fulltext | status,post_date,type,jsd | jsd | 0 | | 1 | Using where; Using filesort |
+-------+----------+---------------------------+--------+---------+--------+------+-----------------------------+
so it's using the fulltext index. can i limit the amount of data it uses in scanning fulltext so that it won't hit the filesort limit.
also are these:
set-variable=sort_buffer_size=256M set-variable=myisam_sort_buffer_size=256M
per thread or global? the machine has 6G of RAM in it.
-jsd-
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
