MySQL Forums
Forum List  »  Triggers

Re: Trigger mayhem on update to MySQL 5.0.17
Posted by: Chris DiMartino
Date: December 26, 2005 11:36PM

We've had the same issues with our replication setup when upgrading from 5.0.16 to .17. I've done the same steps as you, which appears to have resolved 95% of the issue. Unfortunately, there is still for some reason some set of circumstances that is causing the replication to fail in the same manner again and again (approximately 1 out of 10000 insert queries, which we are hitting about once a day). We've also noticed strange behaviors while dealing with this issue: if we connect to the mysql server from one of our other hosts, and do a "show triggers", we do not get the triggers back, or at least not all of them, and we receive warnings (definer not fully qualified). If we run the same "show triggers" statement on the mysql host, and then restart the slave, the problem appears to go away.

We plan to put in a support request (we have a support contract) to attempt to find a solution to this. I can't figure out the common thread in the queries in order to be able to submit a bug report with a repeatable case, so perhaps others can share their experiences with this problem as well and we can figure out what is causing it.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Trigger mayhem on update to MySQL 5.0.17
2044
December 26, 2005 11:36PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.