I am using debian squeeze and mysql 5.1.45. I am trying to use mysqldumpslow
-s c -t 10, but I keep getting the following error:
Can't determine basedir from 'my_print_defaults mysqld' output:
--general_log=on. Does anyone have any idea as to why? I am not getting
anything fr
Yeah, It can only parse the local file. If you expect to parse the remote
one, just download it,haha.
杨涛
我博客1:http://yueliangdao0608.cublog.cn
My 我博客2:http://yueliangdao0608.blog.51cto.com
2010/12/19 Eric Bergen
> I don't think so. mysqldumpslow parses the log file on the loca
I don't think so. mysqldumpslow parses the log file on the local server.
On Fri, Dec 17, 2010 at 3:01 AM, partha sarathy wrote:
> Is it possible to run mysqldumpslow on a remote host?
>
> -Partha
>
>
> --
> MySQL General Mailing List
> For list archives: http
Is it possible to run mysqldumpslow on a remote host?
-Partha
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Anil Doppalapudi wrote:
Hi List,
Any update on this
Thanks
Anil
Hi List,
Below is the output of mysqldumpslow. In the output query execution time is
showing -ve value how to interpret the below output i.e how to interpret
-ve value for query execution time please advice
Nobody has
Hi List,
Any update on this
Thanks
Anil
Hi List,
Below is the output of mysqldumpslow. In the output query execution time is
showing -ve value how to interpret the below output i.e how to interpret
-ve value for query execution time please advice
Count: 1 Time=4294967223.00s
Hi!
>>>>> "Steven" == Steven Roussey <[EMAIL PROTECTED]> writes:
>> Description:
Steven> 1. Handling of string simplification confused, crashes perl!
Steven> 2. Format of slow log had changed a while back, so now the
Steven> timing
>Description:
1. Handling of string simplification confused, crashes perl!
2. Format of slow log had changed a while back, so now the
timing information is broken in mysqldumpslow
>How-To-Repeat:
uploaded to mysql secret: n54-slow.log.gz
gunz
(BTW, mysqldumpslow does not seem to be in the RPMs for v4.)
mysqldumpslow (perl itself, I guess) dumps core and acts incorrectly
when dealing with simplifying strings.
Fix:
Change:
s/'([^\\\']|\\.|\'\')+'/'S'/g;
s/"([^\\\"]|\\.|\&qu
I'm trying to find what causes mysqldumpslow to crash for us every time
the log is anything but trivial. The following does not crash it, but it
does give incorrect results:
# User@Host: apache[apache] @ morpheus.e [1.1.1.1]
# Query_time: 8 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
re
>From the manual (section 4.9.5 'The Slow Query Log'):
"The slow query log can be used to find queries that take a long time to
execute and are thus candidates for optimisation. With a large log, that
can become a difficult task. You can pipe the slow query log through the
mys
Attached is an updated version of the mysqldumpslow command that's
supplied in the mysql distribution.
The mysqldumpslow, for those who've not tried it, makes it very
easy to summarize and analyze the contents of the 'slow query log'.
This update was prompted by the need
12 matches
Mail list logo