… an obvious disclaimer here in that the aforementioned statements reflect only my opinion and not any official …’re not using GTID-based replication. If you are using GTID-based replication, it looks like you’ll … with –skip-grant-tables and insert a few rows into an InnoDB table, but trying to run …
Post: Is Synchronous Replication right for your app?
… effect on standard MySQL replication from this instance, since MySQL replication is asynchronous. What about semi-sync MySQL replication? It’s actually much… just a few hundred rows. When a player makes an achievement, your application updates this table with a statement like this: UPDATE…
Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)
… SLAVE statement also behaves differently: mysql> stop slave; Query OK, 0 rows affected (0,01 sec) mysql > reset slave; Query OK, 0 rows…, you will be able to restart replication, but again as no replication coordinate is specified, replication will start at the beginning of the… all replication-related configuration: mysql> stop slave; Query OK, 0 rows affected (0,00 sec) mysql> reset slave all; Query OK, 0 rows…
Post: Can MySQL temporary tables be made safe for statement-based replication?
… exist for row-based replication in MySQL 5.1 and later, but most installations I know of are using statement-based replication, even on… MySQL statement-based replication without some risk of breaking slaves. At some point I may test how it works with row-based replication; I believe even row-based logging format is going to have some problems, because the CREATE TABLE is logged in statement…
Post: Debugging problems with row based replication
… with row-based replication. Only actual changes are written to the database with row-based logs. Take as an example a DELETE statement which… a statement based binary log. Since row-based logs only contain information about changed rows, a replication slave which does not find a row referenced…
Post: INSERT INTO ... SELECT Performance with Innodb tables.
… and concurrency ? The reason is – replication. In MySQL before 5.1 replication is statement based which means statements replied on the master should cause… sets on statement execution, which generally gives better concurrency. However as the name says it makes locks unsafe fore replication and point… lock structs, which means it has locked a lot of rows. “fetching rows” of course means it is still going. In this…
Post: Estimating Replication Capacity
…: 0 BYTES_SENT: 63 BINLOG_BYTES_WRITTEN: 0 ROWS_FETCHED: 0 ROWS_UPDATED: 127576 TABLE_ROWS_READ: 4085689 SELECT_COMMANDS: 0 UPDATE_COMMANDS… replication the most. It however works only with statement level replication. You need to set long_query_time=0 and log_slave_slow_statements… had log_slave_slow_statements unreliable and also you may need to adjust regular expression for finding users replication thread uses. 3…
Post: STOP: DELETE IGNORE on Tables with Foreign Keys Can Break Replication
… row in set (0.00 sec) An expected behavior for DELETE IGNORE is that if the statement fails to delete all rows, none… slave is out of sync, because the statement failed to delete all intended rows it was not written to the binary log… ROW* based replication. When using the latter, MySQL will log separate statements for each row that is deleted – so if the first 100 rows was…
Post: Replication of MEMORY (HEAP) Tables
… add Replication to your environment as MEMORY tables do not play well with replication. The reason is very simple – both STATEMENT and ROW replication contain… is a little checks whenever statements produce the same results on the slave. ROW replication will complain about ROW not exist for UPDATE or…

