MySQL Bugs: #38462: Binlog file shows incomplete file name in online backup table.

Bug #38462	Binlog file shows incomplete file name in online backup table.
Submitted:	30 Jul 2008 16:12	Modified:	29 Sep 2008 20:47
Reporter:	Hema Sridharan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Backup	Severity:	S3 (Non-critical)
Version:	mysql-6.0-backup, mysql-6.0	OS:	Linux
Assigned to:	Jørgen Løland	CPU Architecture:	Any

Description:
Enable binary logging. create database and tables.
Perform backup database operation and check the online backup table for binlog file and position. The binlog file is not shown completely in the table.

Note that this problem does not occur when tested manually.

How to repeat:
--source include/have_log_bin.inc
CREATE DATABASE IF NOT EXISTS backup;
USE backup;
CREATE TABLE t1 SELECT 1;
SHOW BINARY LOGS;
BACKUP DATABASE backup to 'bin.bak';
--query_vertical SELECT * FROM mysql.online_backup;

Results
========

CREATE DATABASE IF NOT EXISTS backup;
USE backup;
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 SELECT 1;
SHOW BINARY LOGS;
Log_name        File_size
master-bin.000001       385
BACKUP DATABASE backup to 'bin.bak';
backup_id
1
SELECT * FROM mysql.online_backup;;
backup_id       1
process_id      0
binlog_pos      385
binlog_file     /data0/team6.0/mysql-6.0-backup/mysql-test/var/log/master-bin.00
backup_state    complete
operation       backup
error_num       0
num_objects     1
total_bytes     1033
validity_point_time     2008-07-30 15:57:36
start_time      2008-07-30 15:57:36
stop_time       2008-07-30 15:57:36
host_or_server_name     localhost
username        root
backup_file     bin.bak
user_comment
command BACKUP DATABASE backup to 'bin.bak'
drivers MyISAM

Thank you for the report.

Verified as described.

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/54082

2697 Jorgen Loland	2008-09-15
      Bug#38462 - Binlog file shows incomplete file name in online backup table.
      
      Before: Binlog file name was written with full path to 
      backup_history log. The full path could easily be more than 64 
      chars, which is the defined length of this field in the table.
      
      Now: Full path is not needed, only binlog file name.

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/54095

2694 Jorgen Loland	2008-09-15
      Bug#38462 - Binlog file shows incomplete file name in online backup table.
            
      Before: Binlog file name was written with full path to 
      backup_history log. The full path could easily be more than 64 
      chars, which is the defined length of this field in the table.
            
      Now: Full path is not needed, only binlog file name.

Approved.  Good to push.

Good to push.

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/54185

2694 Jorgen Loland	2008-09-15
      Bug#38462 - Binlog file shows incomplete file name in online backup table.
            
      Before: Binlog file name was written with full path to 
      backup_history log. The full path could easily be more than 64 
      chars, which is the defined length of this field in the table.
            
      Now: Full path is not needed, only binlog file name.

Pushed to 6.0 main for 6.0.8

Noted in 6.0.8 changelog.

The binary log filename stored in the binlog_file column of the
mysql.backup_history MySQL Backup table now is the file basename (the
final component). Previously, the full pathname was stored, but this
could be too long for the column width.