3 ms·
Awesome news! My job involves using the current mysql cloud SQL with replication, and boy does it suck. Every schema change (even adding an index) causes the re
by orf 9y ago
Awesome news! My job involves using the current mysql cloud SQL with replication, and boy does it suck. Every schema change (even adding an index) causes the replica to get stuck behind and never catch up. Apparently this is a 'documented limitation' and deleting/recreating the replica is the supposed solution.
Urgh. I'm hoping this is a mysql issue and pg doesn't suffer from this.
- rockostrich 9y agoI would assume this has to do with MySQL's lack of transactional DDL, but I haven't looked into it at all. I actually don't mind MySQL as much as people complain about it, but I haven't dealt with any cases that requires more than a single read replica.
- boundlessdreamz 9y agoReplica as in Read Replica? Are you using V2? We are using read replicas and are not facing any such problems