Bug #40219 backup_{history,progress}_log_file not settable at server startup
Submitted: 21 Oct 2008 19:38 Modified: 15 Nov 2008 1:39
Reporter: Paul Dubois Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Backup Severity:S4 (Feature request)
Version:6.0 bzr OS:Any
Assigned to: Chuck Bell CPU Architecture:Any
Triage: Needs Triage: D5 (Feature request)

[21 Oct 2008 19:38] Paul Dubois
Description:
Recent work has been done to make backup logging more flexible in the same way as the server's general query log and slow query log. However, a recent change to general/slow query logging has not been carried over to backup logging:

* The general_log_file and slow_query_log_file system variables hold the names of the general/slow log filenames.
* These variables were settable at runtime, but not at server startup (on the command line or in option files).
* As part of the work done for WL#4403, these variables now can be set at server startup. (Granted, it's not that obvious from the WL that this has been done, but it has.

The new backup logging work added backup_history_log_file and backup_progress_log_file system variables that hold the names of the backup logging files. However, they can only be set at runtime, and not at server startup.

Please expose backup_history_log_file and backup_progress_log_file so they can be set at server startup.

How to repeat:
Try starting the server with --backup_history_log_file=some_file_name. An unknown variable error will occur.
[21 Oct 2008 20:59] Miguel Solorzano
Thank you for the bug report.
[4 Nov 2008 21:45] 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/57837

2727 Chuck Bell	2008-11-04
      BUG#40219 : backup_{history,progress}_log_file not settable at server startup
      
      The backup_history_log_file and backup_progress_log_file options are not exposed
      for server startup. This patch exposes those options for setting values on
      the command line at server startup.
[6 Nov 2008 14:42] 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/58028

2727 Chuck Bell	2008-11-06
      BUG#40219 : backup_{history,progress}_log_file not settable at server startup
      
      The backup_history_log_file and backup_progress_log_file options are not exposed
      for server startup. This patch exposes those options for setting values on
      the command line at server startup.
[7 Nov 2008 13:54] Øystein Grøvlen
Patch approved.
[8 Nov 2008 10:16] Rafal Somla
Good to push.
[10 Nov 2008 16:49] 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/58350

2729 Chuck Bell	2008-11-10
      BUG#40219 : backup_{history,progress}_log_file not settable at server startup
      
      The backup_history_log_file and backup_progress_log_file options are not exposed
      for server startup. This patch exposes those options for setting values on
      the command line at server startup.
[11 Nov 2008 8:38] 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/58417

2730 oystein.grovlen@sun.com	2008-11-11
      Bug#40219 backup_{history,progress}_log_file not settable at server startup
      Adds test option file that was not pushed with original patch.
[14 Nov 2008 14:50] Bugs System
Pushed into 6.0.9-alpha  (revid:oystein.grovlen@sun.com-20081111083727-ih90523op3rg8m1p) (version source revid:jorgen.loland@sun.com-20081114134411-xypyf8wyjc2nm3ly) (pib:5)
[15 Nov 2008 1:39] Paul Dubois
Noted in 6.0.9 changelog.

The backup_history_log_file and backup_progress_log_file system
variables were not settable at server startup. Now they are.