Article Discussion: How Logs Work On MySQL With InnoDB Tables

How Logs Work On MySQL With InnoDB Tables If you have any questions or comments about this article then please post them here.

You can read the article here .

This is my real situation:

There are several transactions just at one time.
Example:

---TRANSACTION 0 13699445, ACTIVE 659 sec, process no 26481, OS thread id 901142
11 lock struct(s), heap size 1024, undo log entries 7
MySQL thread id 46, query id 45109 Galvanik 10.10.10.26 stn
Trx read view will not see trx with id >= 0 13699446, sees < 0 13686036
---TRANSACTION 0 13689134, ACTIVE 13209 sec, process no 26407, OS thread id 425999
9 lock struct(s), heap size 1024, undo log entries 2
MySQL thread id 17, query id 44823 Texnolog 10.10.10.19 stn
Trx read view will not see trx with id >= 0 13689135, sees < 0 13686036
---TRANSACTION 0 13686886, ACTIVE 16919 sec, process no 26422, OS thread id 507921
4 lock struct(s), heap size 320
MySQL thread id 22, query id 44966 Ekonom 10.10.10.34 stn
Trx read view will not see trx with id >= 0 13686887, sees < 0 13686036

..... etc

Suddenly one of them attempting execute INSERT(!!!) give me error: "1205 Lock wait timeout expired".
Why INSERT can concurrent with other trx's???

Usually I resolve this situation by kiling one of processes. And success probability is correlated by its number of locks.
It is so even if this process locks records at its separate table!

Is there limit for locks?
Where I can correct it?

About my system:

MySQL 4.0.16-max+InnoDB
MyODBC+VisualFoxPro 5.0