MySQL Bugs: #42426: Backup history log details are not updated as operation progresses.

Bug #42426	Backup history log details are not updated as operation progresses.
Submitted:	28 Jan 2009 16:13	Modified:	2 Mar 2009 18:34
Reporter:	Hema Sridharan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	mysql-6.0-backup	OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
The mysql backup documentation in reference manuals says that,

" The backup_history table contains a row for each backup and restore
operation. A row is created when an operation begins and is updated as
the operation progresses"

In reality this is not the case with current backup tree. The backup
history logs show the status of last backup / restore only after completion of specific operation. The backup history table doesn't get updated as the operation progresses. I am not sure whats the expected behavior here.

How to repeat:
Perform a backup that may take few seconds to complete. While backup is ongoing, go to another connection and verify any updates of this backup in backup_history.log. 

Updates can be seen in backup_history log only after completion of backup / restore operation.

Suggested fix:
Either we need to fix this issue or modify the document in accordance to the expected behavior.

This is a documentation discrepency as a result of the changes made in WL#4296. That worklog changed the behaviour of the logging to backup_history table. See WL#4296 (CONOPS) "At the start of an operation (backup or restore), a data structure is created for the operation which will be written to the history log at the end of the operation."

Please change the documentation to reflect this behaviour.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.