6 messages in com.mysql.lists.win32RE: Replication| From | Sent On | Attachments |
|---|---|---|
| Grimes, Shawn | 24 Nov 2000 06:36 | |
| Fredrick Bartlett | 24 Nov 2000 07:32 | |
| Luc Van der Veken | 27 Nov 2000 02:52 | |
| Luc Van der Veken | 27 Nov 2000 03:11 | |
| Pete French | 27 Nov 2000 03:24 | |
| Luc Van der Veken | 29 Nov 2000 09:46 |
| Subject: | RE: Replication![]() |
|---|---|
| From: | Luc Van der Veken (luc...@wimi.be) |
| Date: | 11/27/2000 03:11:13 AM |
| List: | com.mysql.lists.win32 |
Jeezes - I'm sitting here with red cheeks again.
Replication works fine, I just (completely) misread the docs about the server ID in my.cnf: I must have had something about security in mind or about replication from more than one master, because I read "must be different for each master" where it actually says "must be different for each server".
Now I do have one more question: in earlier releases, there was a remark in the docs saying that you can round-robin replication between two servers and do updates on both, later that remark was removed.
Does anyone know why? Is there, as I suspect, a risk involved with unique keys and/or auto-increment fields? If that's all, I think I could still use it, because updates would always be done on just one server - it's just that which server that is might change from time to time, without any overlap ever. Or am I begging for race conditions around the switchover now?
Regards, Luc.




