Re: Update: Status of MySQL 4.0/Innobase/transactions row level locks

2001-02-13 Thread Heikki Tuuri
[...]. Currently, in MySQL you must call UNLOCK TABLES before issuing another LOCK TABLES, because there is no deadlock detection in MySQL itself. I believe a LOCK TABLES does an automatic atomic UNLOCK TABLES of any that were locked before if it's able to get the requested locks. Tim.

Re: Update: Status of MySQL 4.0/Innobase/transactions row level locks

2001-02-12 Thread Heikki Tuuri
Hi! The timeout in Innobase deadlock resolution is configurable in my.cnf file: you will be able to set it in units of one second (or would someone need an even greater precision?). In the future we might modify the MySQL code so that Innobase gets the information of MySQL LOCK TABLES commands

Re: Update: Status of MySQL 4.0/Innobase/transactions row level locks

2001-02-10 Thread Benjamin Pflugmann
Hi. On Fri, Feb 09, 2001 at 05:34:38PM +0200, you wrote [...] 5. Add a timeout to lock waiting: Innobase can detect and resolve deadlocks within its own lock table, but if a user uses also MySQL LOCK TABLES... or BDB locks, a deadlock can occur where Innobase does not know of all the locks: