MySQL Bugs: #59931: The mysqlbackup option --no-history-logging disables progress logging also.

Bug #59931	The mysqlbackup option --no-history-logging disables progress logging also.
Submitted:	4 Feb 2011 2:11	Modified:	7 Feb 2011 23:19
Reporter:	Hema Sridharan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Backup	Severity:	S3 (Non-critical)
Version:	MEB 3.6	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
The new option "--no-history-logging" is introduced in MEB 3.6 version.
This option should disable history logging.
But when --no-history-logging option is used when executing MEB, it also disables progress logging. Meaning the progress states are also not logged and backup_progress table is not created.

How to repeat:
Run mysqlbackup with --no-history-logging option and check for the backup_history and progress tables. You will notice that both tables are disabled.

After backup is performed, we can see the following:
mysql> show tables from mysql like 'backup%';
Empty set (0.00 sec)

mysql> select * from mysql.backup_history;
ERROR 1146 (42S02): Table 'mysql.backup_history' doesn't exist
mysql> select * from mysql.backup_progress;
ERROR 1146 (42S02): Table 'mysql.backup_progress' doesn't exist

As per design, only history logging should be disabled and not progress logging. But if both tables are to be disabled with one option, then option should be renamed as "--no-logging" instead of "--no-history-logging"

Thank you for the report.

Verified as described.

The behaviour is by design. There is no separate option to disable history and progress logging. The term history-logging is loosely used for logging at mysql level. Hence closing this bug.