Dear All,
Today i faced an issue while issuing commands on my innodb tables.
When I issued any drop table or alter table command my query gets into
waiting state for more than 15-20 minutes.
Mysql Version :-5.5.4 community
I researched on the issue and find that every command try to get lock
On 4/5/2012 3:14 PM, Wes Modes wrote:
No one here has any experience with it?
...
Probably not. If you notice the version number for MySQL Proxy still
starts with a 0. which the universally accepted indicator that it is
of pre-production quality. Thanks to the corporate changes of the last
- Original Message -
From: joe j joe.st...@gmail.com
Good suggestion. But I am a perl/unix illiterate. However I may learn
in them future-you never know!
You're never too old to learn :-)
http://tldp.org/LDP/abs/html/
--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't
There is almost no reason to use LOCK TABLES on InnoDB tables.
I prefer to have auto_commit=1, then use explicit BEGIN and COMMIT for
clumps of statements that need ACID. I never use auto_commit=0.
Following those two rules, your issue with innodb_table_locks being on
goes away.
On 4/5/12
