Re: Per query DB stats... ideally for InnoDB

2006-04-21 Thread Samuel Ziegler
> > On Wed, 19 Apr 2006, Samuel Ziegler wrote: > > > To: [EMAIL PROTECTED] > > From: Samuel Ziegler <[EMAIL PROTECTED]> > > Subject: Re: Per query DB stats... ideally for InnoDB > > > > Those functions do give useful information, but as you point out, the

Re: Per query DB stats... ideally for InnoDB

2006-04-19 Thread mysql
: > To: [EMAIL PROTECTED] > From: Samuel Ziegler <[EMAIL PROTECTED]> > Subject: Re: Per query DB stats... ideally for InnoDB > > Those functions do give useful information, but as you point out, the > trick is associating that information with a specific query. For my >

Re: Per query DB stats... ideally for InnoDB

2006-04-19 Thread Samuel Ziegler
Those functions do give useful information, but as you point out, the trick is associating that information with a specific query. For my use, there will most likely be other SQL activity going on at the same time which makes doing a 'SHOW ENGINE ...' before and after the query not very useful. T

Re: Per query DB stats... ideally for InnoDB

2006-04-19 Thread mysql
Is this of any use at all? >From the 5.0.18 manual: 13.5.4.7. SHOW ENGINE Syntax SHOW ENGINE engine_name {LOGS | STATUS } SHOW ENGINE displays log or status information about storage engines. The following statements currently are supported: snip SHOW ENGINE INNODB STATUS (or SHOW INNODB S