Bug #30334 | Is expire_logs_days really a session variable? | ||
---|---|---|---|
Submitted: | 9 Aug 2007 14:58 | Modified: | 21 Aug 2007 17:23 |
Reporter: | Baron Schwartz (Basic Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | Peter Lavin | CPU Architecture: | Any |
[9 Aug 2007 14:58]
Baron Schwartz
[9 Aug 2007 15:23]
MySQL Verification Team
Thank you for the bug report.
[10 Aug 2007 13:21]
Baron Schwartz
A related note: Exec_Master_Log_Pos, Read_Master_Log_Pos, and some other similar variables on http://dev.mysql.com/doc/refman/5.1/en/server-status-variables.html are shown with dual status scope.
[10 Aug 2007 13:55]
Baron Schwartz
In fact, I'm running a MySQL 6.0 Alpha sandbox, and in the output of SHOW STATUS I don't see a bunch of the status variables in http://dev.mysql.com/doc/refman/5.1/en/server-status-variables.html: - Anything to do with slave status - Any of the have_% variables -- I think these are from SHOW VARIABLES I had assumed these were added to 5.1 and hence 6.0, so I didn't comment on this before, but now I don't see them. Apologies if this is too many things in one bug report, but I have a feeling these tables might all be generated from some include files that got a little mixed up.
[21 Aug 2007 17:23]
Peter Lavin
Scope corrected by Paul -- see previous comment. Removed %_Log_pos variables.