03, 2006 1:39 PM
To: Rick James
Cc: Robert DiFalco; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: Re: Innodb Locks
There is a detailed write-up on how locking works in the manual:
http://dev.mysql.com/doc/refman/5.0/en/innodb-transaction-model.html
If you are not doing replication, you might
Schwartz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 1:39 PM
To: Rick James
Cc: Robert DiFalco; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: Re: Innodb Locks
There is a detailed write-up on how locking works in the manual:
http://dev.mysql.com/doc/refman/5.0/en/innodb
; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
We'll do some testing with innodb_locks_unsafe_for_binlog but if this
fixes the problem then it is a pretty safe assumption that the problem
also exists with subqueries in DELETE and UPDATE and not just for that
one case of INSERT as the article points
: Robert DiFalco; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: Re: Innodb Locks
There is a detailed write-up on how locking works in the manual:
http://dev.mysql.com/doc/refman/5.0/en/innodb-transaction-model.html
If you are not doing replication, you might check out
: Re: Innodb Locks
It's not a bug in InnoDB. There are far more knowledgeable people than
I on this list, but it should get a share-mode lock on anything it
selects from, otherwise there might be inconsistencies as it tries to
serialize different transactions into the binary log for replication
: 860.674.8341
-Original Message-
From: Robert DiFalco [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 10, 2006 2:42 PM
To: Baron Schwartz
Cc: Rick James; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
Then I guess I am not understanding why re-writing
@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
It probably uses a single lock to handle a JOIN, and two locks to handle
a sub-SELECT. I doubt that it helps, but if I'm right it will change
what you see when you poking around.
Regards,
Jerry Schwartz
Global Information Incorporated
195
: Robert DiFalco [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 10, 2006 11:50 AM
To: Jerry Schwartz; Baron Schwartz
Cc: Rick James; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
Right, as I understand it the query optimizer in 5.2 will
simply rewrite
these sub selects
Any thoughts on this? Should SomeTable be locked when performing the
UPDATE on AnotherTable?
---
Is there a detailed source for when innodb creates row or table locks?
I have a situation where one thread is performing this in one
transaction:
UPDATE SomeTable SET WHERE
IN (SELECT id FROM t);
-Original Message-
From: Robert DiFalco [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 9:26 AM
To: mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
Any thoughts on this? Should SomeTable be locked when performing the
UPDATE
On 10/2/06, Robert DiFalco wrote:
Is there a detailed source for when innodb creates row or table locks?
The sourcecode.
I have a situation where one thread is performing this in one
transaction:
UPDATE SomeTable SET WHERE SomeTable.id = N;
This is invoked after another thread
To: mysql@lists.mysql.com
Subject: Re: Innodb Locks
On 10/2/06, Robert DiFalco wrote:
Is there a detailed source for when innodb creates row or table locks?
The sourcecode.
I have a situation where one thread is performing this in one
transaction:
UPDATE SomeTable SET WHERE
AnotherTable
SET...
WHERE id IN (SELECT id FROM t);
-Original Message-
From: Robert DiFalco [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 9:26 AM
To: mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
Any thoughts on this? Should SomeTable be locked
Is there a detailed source for when innodb creates row or table locks?
I have a situation where one thread is performing this in one
transaction:
UPDATE SomeTable SET WHERE SomeTable.id = N;
This is invoked after another thread has kicked off this long running
query in another
Heikki,
Yep. That's why I use seperate connections for holding the lock and
to do the subsequent locking attempts. Besides, if that were the
problem, I would see the lock disappear at the very first failed
locking attempt, but that's not the case.
I thought it might be a connection timeout,
Wouter,
the Lock Monitor output tells that trx 370099 has been committed or rolled
back by the user. That is why the locks have disappeared.
Have you taken into account the following:
8.5 When does MySQL implicitly commit or rollback a transaction?
a.. MySQL has the autocommit mode switched
]
Newsgroups: mailing.database.mysql
Sent: Friday, September 06, 2002 7:20 PM
Subject: Re: InnoDB locks disappear
Wouter,
the Lock Monitor output tells that trx 370099 has been committed or rolled
back by the user. That is why the locks have disappeared.
Have you taken into account
Wouter,
- Original Message -
From: Wouter Zelle [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Wednesday, September 04, 2002 10:59 AM
Subject: Re: InnoDB locks disappear
Heikki,
Unfortunately it is not that easy. I've set the
innodb_lock_wait_timeout to 1 because I want
Heikki,
Unfortunately it is not that easy. I've set the
innodb_lock_wait_timeout to 1 because I want locks to fail quickly,
so my program can move on to the next request. In pseudocode:
Fetch a bunch of requests with status=unprocessed
Try to obtain a lock through a select * from x for update
My program uses locks to allow for multi-threading (processing
requests that are stored in the database using more than one thread
and/or application). The problem is that the locks disappear for
seemingly no reason at all. The same queries are repeated over and
over again until the lock just
Wouter,
- Original Message -
From: Wouter Zelle [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, September 03, 2002 7:43 PM
Subject: InnoDB locks disappear
My program uses locks to allow for multi-threading (processing
requests that are stored in the database using
Hi!
Copied message:
..
Hi,
I'm a regular mysql user, and a very newbie to innodb. :)
I would like to use innodb because of its row-level locking feature.
Presently I have to use table locks, and they're causing lots of speed
problems. (I've tried Gemini tables, but mysql always crashed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Tue, 20 Nov 2001, Heikki Tuuri wrote:
When someone buys a particular type of good, I would like to lock those
rows from the table, but since the quantity will change, I don't even want
other users to see these rows until I'm finished.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm a regular mysql user, and a very newbie to innodb. :)
I would like to use innodb because of its row-level locking feature.
Presently I have to use table locks, and they're causing lots of speed
problems. (I've tried Gemini tables, but mysql
24 matches
Mail list logo
