why are these two queries deadlocking?

2005-07-05 Thread Brady Brown
SHOW INNODB STATUS indicates these two queries are deadlocking: (1) REPLACE INTO TMP_pixel_xfer SELECT * FROM user_question q INNER JOIN user_session s USING(user_session_id) WHERE user_question_id BETWEEN '27853011' AND '27891923' ORDER BY s.user_id (2) DELETE t from TMP_user_client_report

we know what is causing now: InnoDB: Warning: using a partial-field key prefix

2005-07-01 Thread Brady Brown
Hi, We have inquired about this warning before, but now that we have upgraded to 4.1, we know which query/table is causing these frequent warnings: 050701 17:19:34 InnoDB: Warning: using a partial-field key prefix in search. InnoDB: index `rp_id` of table `as_imp/roundrobin_pub`. Last data

can innodb_buffer_pool_size be set 2Gb on FreeBSD?

2005-06-17 Thread Brady Brown
Have any of you MySQL/FreeBSD cats successfully set innodb_buffer_pool_size 2G without runing into any of the memory allocation problems found on Linux platforms? Although I have been given good advice to migrate to an AMD platform overcome this limitation (and will do so eventually), I am

What is best open-source platform alternative to overcome innodb 2Gb memory limit on Linux? FreeBSD?

2005-06-15 Thread Brady Brown
Hi, I am currently running a large database (around 20Gb) on a 32bit x86 Linux platform. Many of my larger data-crunching queries are disk-bound due to the limitation described in the innodb configuration documentation: *Warning:* On 32-bit GNU/Linux x86, you must be careful not to set