Comments on: Poor man’s query logging http://www.mysqlperformanceblog.com/2008/11/07/poor-mans-query-logging/ Everything about MySQL Performance Sat, 07 Nov 2009 18:35:44 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: peter http://www.mysqlperformanceblog.com/2008/11/07/poor-mans-query-logging/comment-page-1/#comment-374193 peter Sun, 09 Nov 2008 03:14:45 +0000 http://www.mysqlperformanceblog.com/?p=525#comment-374193 Thanks Charles, Some software is indeed working well even if it was not updated for a while :) Thanks Charles,

Some software is indeed working well even if it was not updated for a while :)

]]> By: Charles-Antoine http://www.mysqlperformanceblog.com/2008/11/07/poor-mans-query-logging/comment-page-1/#comment-374187 Charles-Antoine Sun, 09 Nov 2008 02:57:44 +0000 http://www.mysqlperformanceblog.com/?p=525#comment-374187 This perl script is working fine Peter, I am using it since some time because of the reasons exposed in the post (production environment with general query logging disabled, no downtime possible, poor granularity with the slow query logging on unpatched MySQL servers). You just need libpcap, and some Perl modules (installable easily via the CPAN). By the way, thank you a lot for all the information you are sharing on this blog! This perl script is working fine Peter, I am using it since some time because of the reasons exposed in the post (production environment with general query logging disabled, no downtime possible, poor granularity with the slow query logging on unpatched MySQL servers). You just need libpcap, and some Perl modules (installable easily via the CPAN).

By the way, thank you a lot for all the information you are sharing on this blog!

]]> By: peter http://www.mysqlperformanceblog.com/2008/11/07/poor-mans-query-logging/comment-page-1/#comment-373361 peter Fri, 07 Nov 2008 18:59:52 +0000 http://www.mysqlperformanceblog.com/?p=525#comment-373361 There is also MySQL Query Sniffer. Have anyone tried it ? http://iank.org/querysniffer/ It looks like it was not updated for a while. There is also MySQL Query Sniffer. Have anyone tried it ?
http://iank.org/querysniffer/

It looks like it was not updated for a while.

]]> By: Gregory Haase http://www.mysqlperformanceblog.com/2008/11/07/poor-mans-query-logging/comment-page-1/#comment-373310 Gregory Haase Fri, 07 Nov 2008 15:05:03 +0000 http://www.mysqlperformanceblog.com/?p=525#comment-373310 These issues are generally solved in 5.1. I have a little sql script that I run on occasion when I want to see what's going on: TRUNCATE TABLE `mysql`.`general_log`; SET GLOBAL log_output = 'TABLE'; SET GLOBAL general_log = 'ON'; SELECT SLEEP(60); SET GLOBAL general_log = 'OFF'; If I need to narrow or widen the logging session, I just adjust the sleep time accordingly. I prefer to log to table instead of file because I don't have to have file access on the server to see the log. I can just log into a mysql shell with a SUPER account and search the log with standard SQL syntax. These issues are generally solved in 5.1.

I have a little sql script that I run on occasion when I want to see what’s going on:

TRUNCATE TABLE `mysql`.`general_log`;
SET GLOBAL log_output = ‘TABLE’;
SET GLOBAL general_log = ‘ON’;
SELECT SLEEP(60);
SET GLOBAL general_log = ‘OFF’;

If I need to narrow or widen the logging session, I just adjust the sleep time accordingly. I prefer to log to table instead of file because I don’t have to have file access on the server to see the log. I can just log into a mysql shell with a SUPER account and search the log with standard SQL syntax.

]]>