Hi!
Have you read my previous message on LOCK TABLE canceling?
I see a problem here, problem of deadlocks. If transaction X
locked table A and is going to lock table B, and transaction Y
locked table B and tries to lock A, they will wait for each
other's completion, and that is deadlock. This can be avoided
by introducing adjustable lock wait timeouts. Otherwise it is
a bug.
--
Leon.
---------
"This may seem a bit weird, but that's okay, because it is weird." -
Perl manpage.
