Hello.
According to: http://dev.mysql.com/doc/mysql/en/show-processlist.html the temporary result set was larger than tmp_table_size and the thread is changing the temporary table from in-memory to disk-based format to save memory. I suggest you to play with the value of this variable which is now: tmp_table_size 33554432 Also I think that upgrade to 4.1.11 might solve the problem. The page http://dev.mysql.com/doc/mysql/en/order-by-optimization.html says that MySQL 4.1 and up uses a new faster algorithm for optimization and 'ORDER BY' queries. And maybe some advices from there could be helpful for you. However, I don't see how it is related to replication, except that master makes a lot of requests to read binary logs to send the updates to the slave. Rafal Kedziorski <[EMAIL PROTECTED]> wrote: > I get this: > > id: 52401 > user: omk-write > host: xxxx > db: omk > command: query > time: 0 > State: Copying to tmp table > Info: select distinct m.media_id from category_tree c_tree, > media_2_category m2c, media m, media_2_partner ... > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
