Re: Help interpreting SHOW INNODB Status Message

2004-12-08 Thread Heikki Tuuri
L PROTECTED]> Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Lähetetty: Wednesday, December 08, 2004 12:16 AM Aihe: Re: Help interpreting SHOW INNODB Status Message Heikki, Thanks for the input. Right now we can't move to 4.1, we're stuck with 4

Re: Help interpreting SHOW INNODB Status Message

2004-12-07 Thread Emmett Bishop
p MyISAM > tables > http://www.innodb.com/order.php > > > - Original Message - > From: "Emmett Bishop" <[EMAIL PROTECTED]> > Newsgroups: mailing.database.myodbc > Sent: Tuesday, December 07, 2004 5:44 PM > Subject: Re: Help interpreting SHOW INNOD

Re: Help interpreting SHOW INNODB Status Message

2004-12-07 Thread Heikki Tuuri
t Bishop" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Tuesday, December 07, 2004 5:44 PM Subject: Re: Help interpreting SHOW INNODB Status Message Heikki, We're using MySQL 4.0.20. Here's the full output: = 041207

Re: Help interpreting SHOW INNODB Status Message

2004-12-07 Thread Emmett Bishop
Heikki, We're using MySQL 4.0.20. Here's the full output: = 041207 8:33:26 INNODB MONITOR OUTPUT = Per second averages calculated from the last 15 seconds -- SEMAPHORES -- OS WAIT ARRAY INFO: reservation coun

Re: Help interpreting SHOW INNODB Status Message

2004-12-07 Thread Heikki Tuuri
Emmett, - Original Message - From: "Emmett Bishop" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Tuesday, December 07, 2004 6:01 AM Subject: Help interpreting SHOW INNODB Status Message Howdy all, We're having concurrency problems with a table in our

Help interpreting SHOW INNODB Status Message

2004-12-06 Thread Emmett Bishop
Howdy all, We're having concurrency problems with a table in our database and I'm not sure if I'm interpreting the following chunk of output from SHOW INNODB STATUS correctly. >From what I gather, the row could not be inserted because the table was locked. I think that this insert was a victim o