why did they change this? I reverted everything to 5.0.19 and I'm
using load data infiles again, with zero locking issues
It has always been like that.
load data infile seems to use different logic from replace delayed,
it does not lock at all
What table type do you have in each version?
We have used the same code & myisam tables for a few years, load data
infile concurrent always worked
under 5.0.24 load data infile concurrent started locking tables, we have
reverted back to 5.0.19 and everything is fine again
only 1 data load is a replace, even that one did not have this issue before
I think insert ignore/replace with a low_priority may be a solution for
us, the concurrent reads are all very fast, with the exception of one
slow query every 5-10 minutes, these were/are the problem sql's, and
there's no way to eliminate them
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
