From: Date: August 29 2007 10:46am
Subject: Re: innodb engine status
List-Archive: http://lists.mysql.com/mysql/208775
Message-Id: <829b199c0708290146y3d5d6ba6kd7ffa247bf5767d0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_729_15691714.1188377172281"

------=_Part_729_15691714.1188377172281
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks a lot Alex.

regards
anandkl


On 8/29/07, Alex Arul Lurthu <alex.lurthu@stripped> wrote:
>
> To have a good understanding on the show innodb status output checkout http://www.mysqlperformanceblog.com/2006/07/17/show-innodb-status-walk-through/
>
>
> One area you can look at is the "LATEST DETECTED DEADLOCK". But in most
> cases have found calculations on the status variables more helpful.
>
> --
> Alex
> http://alexlurthu.wordpress.com
>
> On 8/29/07, Ananda Kumar <anandkl@stripped> wrote:
> >
> > Hi Friends,
> >
> > When i do "SHOW INNODB STATUS\G". It gives me details of transaction
> > happening on INNODB engine.
> >
> > Please let me know what all information i should consider from this
> > output
> > to ensure if everything is fine or there are issue which i should
> > address.
> >
> > I am using mysql version "5.0.41-community-log"
> >
> > regards
> > anandkl
> >
>
>
>
>
>

------=_Part_729_15691714.1188377172281--