> It could be a dump of entire table for replication, slave
registration,
> create / drop db etc ..
While I may have found a bug, I doubt then that I found the right one.
:( I finally started going back through the stack trace.
Just to save my sanity, are you sure 'slowlog' works for you?
I tried running 4.0.3 under no load and executed just one fulltext
select query (took 11 seconds). The only thing in the slow log was the
header:
/root/mysql-4.0.3-beta-pc-linux-gnu-i686/bin/mysqld, Version:
4.0.3-beta-log, started with:
Tcp port: 3306 Unix socket: /tmp/mysql.sock
Time Id Command Argument
However, there was nothing about the query. ??? (4.0.2 works correctly)
But it did not crash either. Shutting the server down did not flush
anything to disk.
Hey... I just looked through the whole slow query log. What I did _not_
notice in the log were *any* fulltext searches when 4.0.3 was running.
Usually that is the bulk of them. Has anything changed related the that?
Maybe now you can try a test case of a full text search with slowlog
activated and do a long FTS select and see if it logs it... I'll look
through the source more in the morning...
Sincerely,
Steven Roussey
http://Network54.com/?pp=e
