Hi,
I'm running mysql 4.0.1.max on freebsd 4.4-stable. I have a fairly high
volume db server which is user to processe approx 200 apache hits/sec. After
previously having problems with 4.0.0 I changed to 4.0.1 and everything
seemed fine for about 4 days. The exact same queries happen almost every 2
seconds. After 4 days I suddenly got the following error, one which I used
to get much more frequently with 4.0.0.
DBD::mysql::st execute failed: Deadlock found when trying to get lock; Try
restarting transaction at
/usr/local/lib/perl5/site_perl/5.6.1/i386-freebsd/Mysql.pm line 172.
The script executing these queries is written in perl and I'm using mysql
modules version Msql-Mysql-modules-1.2219 by Jochen Wiedmann.
Can someone please explain to me what exactly this error means, or rather I
know what a deadlock is but how it can possibly occur after 4 days of
executing the same queries thousands of times. Should the dbms not roll back
the query automatically and carry on?
How can I add functionality in my perl script to stop this error killing the
application or must I just put it in a while(1) bash loop?
Any help much appreciated
Richard
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
