|
|||||||||||
|
Re: profiling question
From: Chad MILLER <cmiller(at)mysql.com>
Date: Mon Aug 13 2007 - 07:42:49 EDT
On 12 Aug 2007, at 12:26, Vangelis Katsikaros wrote:
The session's history-size is set from the global size when the session is created. You may think of it as a default value. > Also I would like to ask if there is a reason for not having Yes, it's intentional. Profiling is expensive, and it should never be left on. This is a safeguard against our users who don't read the manual. Furthermore, profiling data is session-specific. Outside of a session, there's no way to access the profiling data. Thus, it doesn't make sense to enable profiling from outside, when one can't access it from outside. Now, it would be nice to create a way to write "remote" profiling data to a table. Say, I'm in connection 23 and I want profiling data on connection 42 (or some expression that describes the session), it would be nice to turn on profiling and write its results to a particular table that I name. I invite that feature to be implemented.
-- Chad Miller, Software Developer chad@mysql.com MySQL Inc., www.mysql.com Orlando, Florida, USA 13-20z, UTC-0400 Office: +1 408 213 6740 sip:6740@sip.mysql.comReceived on Mon Aug 13 07:43:07 2007 This archive was generated by hypermail 2.1.8 : Sun Oct 07 2007 - 07:59:12 EDT |
||||||||||
|
|||||||||||