MySQL Bugs: #87169: Request to enhance documentation deleted by webmaster

Bug #87169	Request to enhance documentation deleted by webmaster
Submitted:	23 Jul 2017 9:32	Modified:	26 Jul 2017 12:39
Reporter:	Roland Giesler	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I added a comment to this documentation page: https://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html

My comment/request:
It would be good if someone could expand a little on this feature.  Some
aspects here are not obvious.

In which database should the 'innodb_monitor' table be created?

Where does the logging take place?  In the table?  Somewhere else?

It would make this section more useful.

================

Then I got this response, which is non-sensical imho.

The user comment system in the MySQL manual is not the place to
request features. You can do so using our bug-tracking system at
https://bugs.mysql.com/. Thanks.

Read our comment policy for further details:
https://dev.mysql.com/doc/comment-policy/

================

So I'm filing this bug, since there doesn't seem another option.

How to repeat:
Read the documentation page

Suggested fix:
Enhance to the documentation to fully describe the feature and not just refer to it casually as is the case at the moment.

Verified.

Posted by developer:
 
This section has been revised:
https://dev.mysql.com/doc/refman/5.5/en/innodb-enabling-monitors.html

"When InnoDB monitors are enabled for periodic output, InnoDB writes the output to the mysqld server standard error output (stderr). InnoDB sends diagnostic output to stderr rather than to stdout or fixed-size memory buffers to avoid potential buffer overflows.

On Windows, stderr is directed to the default log file unless configured otherwise. If you want to direct the output to the console window rather than to the error log, start the server from a command prompt in a console window with the --console option. For more information, see Error Logging on Windows.

On Unix and Unix-like systems, stderr is typically directed to the terminal unless configured otherwise. For more information, see Error Logging on Unix and Unix-Like Systems."

"Using CREATE TABLE syntax is just a way to pass a command to the InnoDB engine through MySQL's SQL parser. The only things that matter are the table name and that it be an InnoDB table. The structure of the table and the database where the table is created are not relevant."

Thank you for the bug report.

Excellent, that's good and much appreciated!