July 09, 2009 1:22 PM
> To: Walton Hoops
> Subject: Re: Lock timeouts
>
> You have no index for 'Weekend' which means that InnoDB can't just
> lock the appropriate rows.. it' does not know which rows will be
> affected until it has touched ALL of them. Try cre
Forwarded response from Micheal. I haven't tested it yet (have to wait till
I have more data to move), but this sounds about right.
Thanks!
-Original Message-
From: Michael Dykman [mailto:mdyk...@gmail.com]
Sent: Thursday, July 09, 2009 1:22 PM
To: Walton Hoops
Subject: Re:
o:wal...@vyper.hopto.org]
Sent: Thursday, July 09, 2009 2:12 PM
To: mysql@lists.mysql.com
Subject: Lock timeouts
Oh wise and all knowing MySQL Guru's:
I've been running into a problem recently that has be confused.
I have 2 tables, both with the structure:
DROP TABLE IF EXISTS `a
Oh wise and all knowing MySQL Guru's:
I've been running into a problem recently that has be confused.
I have 2 tables, both with the structure:
DROP TABLE IF EXISTS `acn_market_level`.`market_scans`;
CREATE TABLE `acn_market_level`.`market_scans` (
`Retailer` char(3) NOT NULL,
`Marketkey` int(11)
(IOD)
-
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
Date: Tue, 1 Oct 2002 15:00:37 +0300
To: "\"iod iod\"" <[EMAIL PROTECTED]>
Subject: Re: InnoDB AUTO-INC lock timeouts / deadlocks on inserts (using
> IOD,
>
> thank you for t
}
if (lock_print_waits) {
printf("Lock wait for trx %lu ends\n",
- Original Message -
From: ""iod iod"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, October 01, 2002 11:10 AM
Subject: Re: InnoDB AUTO-INC lock timeouts / deadlocks on
.
regards,
IOD
Subject: Re: InnoDB AUTO-INC lock timeouts / deadlocks on inserts
(using
> Iod,
>
> - Original Message -
> From: ""iod iod"" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.mysql
> Sent: Thursday, September 26,
Iod,
- Original Message -
From: ""iod iod"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Thursday, September 26, 2002 8:14 AM
Subject: InnoDB AUTO-INC lock timeouts / deadlocks on inserts (using
>
> We have been using InnoDB with
tables. Note that these tables have indexed fields
which are 'INT' & 'AUTO_INCREMENT'.
We are getting lock timeouts on concurrent inserts (in concurrent TRANSACTIONS) very
frequently, although it works fine for a single non-concurrent transaction. Removing
transactions eli
