Archive for the ‘MySQL’ Category
mysqlreport v3.5 released
mysqlreport v3.5 has been released which has the following fixes, changes, updates:
- Fixed bug: incorrect checking of MySQL version caused mysqlreport to ignore InnoDB status values in some cases. Simplified version from 3 integers (major, minor, patch) to 1 (50024 = 5.0.24, 60001 = 6.0.1, etc.) for easier, more accurate version checking all around.
- Fixed potential bug: read_relative_infiles might have incorrectly divided infiles with multiple status value sets.
- Fixed bug: if wait_timeout was greater than –relative, mysqlreport would lose its connection while sleeping. Now the connection is closed and reopened for each live relative report collection.
- Infiles can now be given SHOW VARIABLES output (in addition to the old method of inserting values manually like: key_buffer_size=128M)
- Slow query time is beautified for microsecond, millisecond, and second resolution (format_u_time):
0.000000 – 0.000999 = 0 – 999 µ
0.001000 – 0.999999 = 1 ms – 999.999 ms
1.000000 – n.nnnnnn = 1 s – n.nnnnn s - Added a lot more debugging output.
mysqlreport v3.4a released, bug fix again
mysqlreport v3.4a is ready which, like the recently released v3.4, fixes a bug in the relative reports. This time, it was the InnoDB reports which were not correct when made relative. Changes in v3.4a are:
- Fixed bug: InnoDB report values were wrong in relative reports because 13 InnoDB status values needed to be excluded from being made relative. (thanks Debbie)
- Changed InnoDB Buffer Pool Read ratio to Read hit %
The Guide to Understanding mysqlreport has been accordingly updated, too.
mysqlreport v3.4 released, bug fix
mysqlreport v3.4 is ready which primarily fixes a bug in v3.3 concerning infiles for relative reports.
Changes in v3.4 are:
- Fixed bug: –relative infiles wouldn’t work unless the SHOW STATUS values were prefixed with a line matching: /Variable_name[\s|]+Value/. Now mysqlreport looks for Aborted_clients which should always be present. (thanks Debbie)
- Fixed formatting problem: Created Temp Table Size was too small for >99M
- Removed redundant %Total: column label from Slow line
- Added more debug info
mysqlreport v3.3 released
mysqlreport v3.3 is ready. Changes:
- –all is now the default option and all the sub-report options like –dms, –sas, etc. have been removed. All reports that can be made are made automatically.
- Slow line now displays long_query_time and log_slow_queries
- Created Temp Table line now displays tmp_table_size
- The mysqlreport tgz and zip now extract into their own directory
The mysqlreport Documentation and The Guide To Understanding mysqlreport have been updated to reflect these changes.
mysqlreport v3.2 released
mysqlreport v3.2 has been released. Mark Leith’s post, Aggregating SHOW STATUS Output, reminded me that a user had asked me a few months ago to do this for mysqlreport. I forgot until Mark’s post.
I have finished implementing this feature with mysqlreport. The new version has three new command line options: –relative (-r), –report-count (-c), and –detach. All of these are explained in the doc. This feature required substantial alterations to the script, so please tell me if anything doesn’t work.