Replication - Binary log parsing(Tableid generation, ON DELETE CASCADE handling, Changed columns for update event)
I am using MySQL 5.5 with InnoDB engine. I have set binlog format as row-based replication. I have some doubts regarding replication: 1) How is the tableID generated? Is it stored somewhere? 2) ...
I am trying the following command to extract SQL statements from binlog for using it in another database (Amazon RDS) mysqlbinlog /var/lib/mysql/binlog.000027 --start-position=54375264 ...
I've used PURGE BINARY LOGS as well as FLUSH LOGS, but the mysql directory still contains these files: mysql-bin.000025 mysql-bin.000024 mysql-bin.000023 mysql-bin.000022 mysql-bin.000021 ...
Background I am trying to recover a few thousand rows that were accidentally deleted from a MySQL database. Luckily replication is enabled, so in the binary logs I have a record of each INSERT, ...
Has anyone experienced this? Data replicates fine but when output in mysqlbinlog there are hidden characters that break the input? mysqlbinlog Ver 3.3 for Linux at x86_64 mysql 5.5.28 server ...