Timeline for Is MySQL Replication Affected by a High-Latency Interconnect?
Current License: CC BY-SA 3.0
6 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 8, 2011 at 12:56 | history | made wiki | Post Made Community Wiki by Richard | ||
Aug 7, 2011 at 18:23 | history | edited | Richard | CC BY-SA 3.0 |
added 531 characters in body
|
Aug 7, 2011 at 18:16 | comment | added | Richard | Ooh, good point about not using LIMIT with UPDATE and DELETE. I'll modify my answer to remove that. | |
Aug 5, 2011 at 16:13 | comment | added | RolandoMySQLDBA | BTW Please do not use LIMIT with UPDATE and DELETE statements because the order of rows being updated or deleted may not be the same on the Slave as is on the Master. If fact, warning messages about this appear something like "Statement Not BinLog-Safe" in the error log. | |
Aug 5, 2011 at 16:07 | comment | added | RolandoMySQLDBA | You get a +1 for mentioning how MySQL Replication is single-threaded, but I need to qualify your statement as follows: MySQL Replication is dual threaded using an I/O Thread for downloading SQL Events From Master to Slave and an SQL Thread for processing the SQL Events locally on the Slave. Yet, transmission of the SQL Events is single-threaded, which is contextually correct for this question. | |
Aug 5, 2011 at 15:24 | history | answered | Richard | CC BY-SA 3.0 |