Bug #40878 Backup: main.implicit_commit fails in pushbuild
Submitted: 20 Nov 2008 10:21 Modified: 26 Nov 2008 16:14
Reporter: Jørgen Løland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Backup Severity:S3 (Non-critical)
Version:mysql-6.0-backup v6.0.8 OS:Any
Assigned to: Jørgen Løland CPU Architecture:Any

[20 Nov 2008 10:21] Jørgen Løland
Description:
main.implicit_commit           [ fail ]

mysqltest: In included file "./include/implicit_commit_helper.inc": At line 3: query '$statement' failed: 1752: Database 'db1' already exists. Use OVERWRITE flag to overwrite.

The result from queries just before the failure was:
< snip >
drop event ev2;
CALL db1.test_if_commit();
IMPLICIT COMMIT
YES
#
# SQLCOM_BACKUP
#
INSERT INTO db1.trans (a) VALUES (1);
backup database db1 to 'backup_db1.ba';
CALL db1.test_if_commit();
IMPLICIT COMMIT
YES
#
# SQLCOM_SHOW_ARCHIVE
#
#
# SQLCOM_RESTORE
#
INSERT INTO db1.trans (a) VALUES (1);
restore from 'backup_db1.ba';

More results from queries before failure can be found in /dev/shm/var-n_mix-130/log/implicit_commit.log

Stopping All Servers
Restoring snapshot of databases

How to repeat:
Run mtr on main.implicit_commit

Suggested fix:
Add 'OVERWRITE' flag to RESTORE command
[20 Nov 2008 14:01] 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/59381

2741 Jorgen Loland	2008-11-20
      Bug#40878 - Backup: main.implicit_commit fails in pushbuild
      
      Add 'OVERWRITE' flag to RESTORE
[20 Nov 2008 14:03] Rafal Somla
Good to push.
[24 Nov 2008 10:23] Jørgen Løland
Pushed to backup tree v6.0.8
[24 Nov 2008 13:18] Jørgen Løland
Wrong version... That should be 6.0.9
[26 Nov 2008 8:50] Bugs System
Pushed into 6.0.9-alpha  (revid:jorgen.loland@sun.com-20081120140327-o6xvoljn6wfm4fm7) (version source revid:jorgen.loland@sun.com-20081126084449-lq9ckif3hmxesy1n) (pib:5)
[26 Nov 2008 16:14] Paul Dubois
Test case changes. No changelog entry needed.