I would assume that if you have two MySQL threads, one doing the ugly ALTER TABLE and another responsible for a simple SELECT query (perhaps even query cached) on a table in another database, that no matter how long that ALTER TABLE thread took, the OS would schedule the SELECT thread soon enough and you'd still get timely results.
Just curious, are you using FreeBSD? --- Dan Edwards <[EMAIL PROTECTED]> wrote: > I have a mysql server containing multiple databases, one of the > databases is very important that it is not slowed down by other > databases. This database is used for a real time game server (card > games), and any stalls causes all players to stall, they hate that. I've > mostly solved this problem with a master/slave setup. The problem now is > the other databases in the same mysql instance are getting larg. When I > make changes to them with alter table, it can slow down and even block > queries to the other databases for minutes at a time. My question is how > do I prevent alter table in one database from blocking queries in > another database? What I need is some way to say that any queries to > this database (or specific tables) have top priority, always. > > Thanks for any assistance! > Dan > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
