[DaiTengu]

Originally Posted by kmike

Nothing can prevent you from creating a new table in the replicated db on the slave - granted your db user has the create/update privileges on that db. So your assertion that the slave is read-only isn't true.

(Actually nothing prevents you from messing with replicated tables on the slave, too - which obviously will break the replication integrity)

Sure there is, you can put a read-only option in my.cnf to prevent users from writing data to the database (except for the replication user & the root user)


Anyway, I am also running into the results out of order bug. I haven't changed anything, and it just seemed to start cropping up one day.