Hi folks, I have a bit of a problem. I'm running 3.23.53 which I've compiled up from source (because the RPMs are not an option for me).
I have a process that does a fairly large select statement every 10 minutes - up until a few days ago it was all find and dandy. A few days ago I did a massive delete from one of the tables (getting rid of a lot of old records), and since then things have gone awry. The select statement seems to get "stuck" in the "COPY TO tmp table" stage, and starts to back up fairly heavily. Each of the cron-run processes gets to this "COPY TO TMP TABLE" stage and locks up, which consumes all available slots on the server and the whole things comes to a grinding halt. I've already run an optimize table on the table, and that got rid of all the "empty space" freed up by the delete. Any ideas why, after the massive delete, things have started slowing right down (or locking up entirely)? THanks for help. -Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
