469,110 Members | 1,894 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,110 developers. It's quick & easy.

replication and internals

------=_NextPart_000_000C_01C36344.47734B10
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Replicating queries where re-written to fix various bugs, most notably
time and auto-increment bugs. Why doesn't replication also enforce
rewriting INSERT INTO into INSERT DELAYED / etc. I've notice that the
replicating thread in 3.23.5x will wait for a table instead of going
onto another log event iff that table is being queried. I would think
adding DELAYED under the covers for replication would be a big win for
mysql, in keeping a slave consistent and up to date.

What would the drawback be? It's not waiting for an auto increment value
to be returned is there some other intrinsic problem?
This should be a win win for both 3.5x and 4.x

------=_NextPart_000_000C_01C36344.47734B10--
Jul 19 '05 #1
0 1142

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Cherrish Vaidiyan | last post: by
reply views Thread by Dathan Vance Pattishall | last post: by
1 post views Thread by zero_addiction | last post: by
3 posts views Thread by dlesandrini | last post: by
9 posts views Thread by David W. Fenton | last post: by
3 posts views Thread by Gert van der Kooij | last post: by
1 post views Thread by CARIGAR | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.