Bug #29589 | sys_innodb_max_purge_lag is defined twice in sys_variables | ||
---|---|---|---|
Submitted: | 6 Jul 2007 2:13 | Modified: | 24 Oct 2007 2:53 |
Reporter: | Sadao Hiratsuka (Basic Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.42 | OS: | Any |
Assigned to: | Damien Katz | CPU Architecture: | Any |
Tags: | innodb_max_purge_lag, set_var.cc, sys_variables |
[6 Jul 2007 2:13]
Sadao Hiratsuka
[6 Jul 2007 11:13]
Sveta Smirnova
Thank you for the report. Verified as described.
[9 Jul 2007 13:40]
Heikki Tuuri
This may be better classified as a MySQL bug, since InnoDB developers do not have access to set_var.cc.
[28 Sep 2007 21:13]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/34668 ChangeSet@1.2524, 2007-09-28 17:13:35-04:00, dkatz@damien-katzs-computer.local +1 -0 Bug #29589 sys_innodb_max_purge_lag is defined twice in sys_variables Removed duplicate innodb variable from sys_variables array.
[15 Oct 2007 18:32]
Damien Katz
pushed to 5.0-runtime, 5.1-runtime and 5.2-runtime
[19 Oct 2007 18:53]
Bugs System
Pushed into 5.1.23-beta
[19 Oct 2007 18:54]
Bugs System
Pushed into 5.0.52
[24 Oct 2007 2:53]
Paul DuBois
No user-visible effect. No changelog entry needed.