innobase_query_caching_of_table_permitted error?

I just upgraded MySQL from 4.1.14 to 5.0.16 and I'm getting the following error over and over again in my server log. 051213 15:55:21051213 15:55:21 [ERROR] The calling thread is holding the adaptive search, latch though calling innobase_query_caching_of_table_permitted. I haven't been able to n

Re: Correct way to use innodb_file_per_table?

Heikki, > the best way would be to symlink whole database directories under the > datadir. Then also an ALTER TABLE keeps the new .ibd file on > the drive you > intended it to be on. If you symlink a single .ibd file, then > an ALTER will > create the new .ibd file as not symlinked. > > As a

Correct way to use innodb_file_per_table?

I've added a second drive to my database machine and want to split my database tables between the two drives to balance the load and improve performance. I know I'll need to drop and restore the db to get MySQL to create the tables in their own files. What's the correct way to use innodb_file_per_t

optimize table and replication failure

I issued a optimize table statement on my master which failed with a "lock wait timeout" message due to some competing queries running at the same time. Now the statement has been replicated to my slaves, and it completes successfully. However it's killing the slave input thread with the following

temporary tables, replication, and innodb tables

I'm working on a new series of queries that share a temporary table. I've tried using both "create temporary table select" and "create temp table" then "insert into t ... select from y". Both seem to create a lock that (if the select portion runs long enough) causes a deadlock with the replica