Re: InnoDB behaviour with multiple clients

2001-07-16 Thread Heikki Tuuri
'conservative locking' in literature). Regards, Heikki http://www.innodb.com At 03:01 PM 7/10/01 +0300, you wrote: >Content-Type: message/rfc822 >Content-Description: forwarded message >Content-Transfer-Encoding: 7bit > >Subject: InnoDB behaviour with multiple clients &g

Re: InnoDB behaviour with multiple clients

2001-07-10 Thread Peter Zaitsev
Hello Denis, Tuesday, July 10, 2001, 12:51:40 PM, you wrote: If I'm not mistaken the problem is - conflicting transactions which you have here. I'm really not shure INNODB dead lock detection is quite fine graned. Also it's shurely may roll back more long running transaction. But anyway you

InnoDB behaviour with multiple clients

2001-07-10 Thread Denis Pithon
Hi all, I begin to validate MySQL with InnoDB on our platform. I use a DBI perl test which manages a data pool reflecting exactly the rows stored in DB. This test internally builds some new data to insert and chooses rows to delete and update (the tables are chosen randomly). Then all these opera