On Tue, 04 Sep 2012 01:50:42 +0200 Reindl Harald <h.rei...@thelounge.net> wrote:
> > Like this > > http://www.iheavy.com/2012/04/26/bulletproofing-mysql-replications-with-checksums/ > > * mixed transactional and non-transactional tables > not relevant in this context > why would someone mix innodb/myisam a database and transaction? > > * use of non-deterministic functions such as uuid() > not relevant in this context > > * stored procedures and functions > not relevant in this context > > * update with LIMIT clause > not relevant in this context > even if, combined with a clear "order by" no problem > > for postfix lookup tables you have usually a very simple > database scheme with very few changes and 99.9% of all > queries are readonly because postfix does even not need > any write permissions to the database (and does not have > it in any of my setups) > > so you have a simple webinterface for updates or if > you have only a few domains/users maybe phpMyAdmin or > terminal would be enough > > so there is virtually zero danger for get out of sync Thank you very much for the answer, it covers all my questions in full detail. Why someone would use something like uuid() on the primary database and then call it an error when it does not work on the slave, I can not understand. Thank you for clearing that up to.
