Bug #30498 | mysqldumpslow isn't documented | ||
---|---|---|---|
Submitted: | 19 Aug 2007 19:34 | Modified: | 20 Aug 2007 9:33 |
Reporter: | Baron Schwartz (Basic Quality Contributor) | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any | |
Tags: | qc |
[19 Aug 2007 19:34]
Baron Schwartz
[19 Aug 2007 22:57]
Paul DuBois
This will not be done until Bug#25855 is handled. That is, a developer needs to address the mysqldumpslow problems described there before a proper manual section can be written.
[20 Aug 2007 9:33]
Stefan Hinz
Unfortunately, there's nothing we can do about this until the underlying "cause" is fixed; see bug #25855: http://bugs.mysql.com/bug.php?id=25855. mysqldump is a third-party tool which doesn't seem to be actively developed any more. We can't document what we don't understand.
[12 Jan 2009 17:40]
Paul DuBois
mysqldumpslow is documented in the manual now: http://dev.mysql.com/doc/refman/5.1/en/mysqldumpslow.html