[MDEV-692] LP:657294 - Replication breaks when upgrading to MariaDB from MySQL 5.0 Created: 2010-10-09  Updated: 2020-05-28

Status: Open
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.0.0, 5.5.28, 5.3.9, 5.5, 10.0
Fix Version/s: None

Type: Bug Priority: Trivial
Reporter: Sergei Golubchik Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug657294.xml    

 Description   

When upgrading a MySQL 5.0 master to MariaDB 5.1, replication breaks on the
slave(s):

Last_Error: Error 'Table 'tablename' already exists' on query. Default database:
'greylist'. Query: 'RENAME TABLE `#mysql50#tablename` TO `tablename`'

The RENAME TABLE shouldn't be replicated.

To reproduce,

  • start MySQL 5.0 server with binary log enabled;
  • create table `t-t` (i int)
  • stop server;
  • start MariaDB server on the same datadir;
  • run mysql_upgrade;
  • grep binary log for 'rename'

 Comments   
Comment by Rasmus Johansson (Inactive) [ 2010-10-09 ]

Launchpad bug id: 657294

Comment by Elena Stepanova [ 2012-11-03 ]

It's still reproducible on current 5.3, 5.5, 10.0 (I didn't check 5.1 and 5.2, but don't see why they would be any different). However, I hope there are not so many people left to upgrade from 5.0, so I'm setting it to Minor.

Generated at Thu Feb 08 06:30:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.