If you are generating links to your blog articles via some other mechanism than Wordpress itself you usually have to use the guid database field. This is the unique global indentifier of the post. In reality it is not globally unique but only unique to your blog. Read more…
I have been encountering a strange error that causes MySQL replication to stop working without any errors reported via SHOW SLAVE STATUS. The command reports everything running ok and that the slave is caught up with the master (seconds behind master=0).
However, looking into the running processes via SHOW FULL PROCESSLIST I noticed that the thread reading the binary log data from the master has disappeared mysteriously.
Read more…
We all know that we should backup our data regularly. This is doubly true when it is not our data but our employers data that we are entrusted with. There are two parts to any successful backup strategy: backup and restore. Often, the restore part is left as an exercise to the reader once needed. I will outline a few tip in this blog for how to make a simple and effective backup processes for a MySQL database. Read more…
MySQL version 5.1 was released today as GA (Generally Available) which means that you can feel safe in using it in a production environment. Of course, any DBA worth their weight in salt should always test any new version personally before flipping the proverbial switch. If there is no need to upgrade (you don’t need the new features) then there is no reason to take the risk. As MySQL founder Monty points out on his blog, no release is perfect and 5.1 still has some bugs left in this release which, he feels, should have been addressed a while ago. Read more…
Replication is a feature of MySQL that allows one database server to mirror the data on another database server by executing the same queries. There are more complicated ways of setting it up but basic replication involves one master server and one slave server. Read more…
I have noticed strange behavior with MySQL version 5 and replication. I manage several MySQL database servers. The setup is simple, one master and two replication slaves acting as backups. The master server version is 5.0.22-log and the two slaves are 5.0.51a and 5.0.45.
When the replication gets interrupted (either via a clean server shutdown or a forced one), replication refuses to restart citing the following error:
ERROR 1201: Could not initialize master info structure, more error messages can be found in the MySQL error log