My OperaBack to our primary master database
By Cosimo Strepponecstrep. Thursday, November 19, 2009 6:09:25 PM
My Opera is now back to our more powerful primary master database.
In fact, since the switch we have been running on our secondary (as primary
Now our old primary, that became secondary, is the primary again.
We officially switched part of the My Opera database to InnoDB. This has been on the wishlist for such a long time... Now it's finally done. But it's not over. We need to proceed the conversion for all our slaves. This will happen "in the background"...
The failover procedure was really smooth. We're getting better at it, and we plan to automate it completely. I'm not sure if we will ever achieve this, but it doesn't seems to be really hard.
We already have a
Someone the other day on this blog asked about Postgres. I really like Pg, I used it for so many years. MySQL can be good too. We'll see...
In fact, since the switch we have been running on our secondary (as primary
Now our old primary, that became secondary, is the primary again.
We officially switched part of the My Opera database to InnoDB. This has been on the wishlist for such a long time... Now it's finally done. But it's not over. We need to proceed the conversion for all our slaves. This will happen "in the background"...
The failover procedure was really smooth. We're getting better at it, and we plan to automate it completely. I'm not sure if we will ever achieve this, but it doesn't seems to be really hard.
We already have a
switch-master script that we can launch against each slave database, and it will safely switch the master db, checking that everything is in order, and it worked quite well today.Someone the other day on this blog asked about Postgres. I really like Pg, I used it for so many years. MySQL can be good too. We'll see...
You must be 
Esteban Manchado Velázquezzoso # Thursday, November 19, 2009 6:34:43 PM
Nicolas Mendozanicomen # Thursday, November 19, 2009 6:36:34 PM
selurus # Thursday, November 19, 2009 8:22:27 PM
Tamil # Thursday, November 19, 2009 10:06:18 PM
Daniel HendrycksDanielHendrycks # Thursday, November 19, 2009 10:24:03 PM
Charles SchlossChas4 # Friday, November 20, 2009 5:00:24 AM
Matt Coxcoxy # Friday, November 20, 2009 11:22:10 AM
Шуйский Николай [krigstask, Ŝtérkrìg]Sterkrig # Friday, November 20, 2009 11:34:26 AM
I asked.
I meant, were there performance tests of some kind before choosing RDBS, or some other reasons to pick out MySQL? Just plain interest, I looked up comparisons (for my work project) and PostgreSQL beats MySQL on highload-systems completely. MySQL is all right for small sites with lots of reads and few writes, but on server like My.Opera you're stuck with "fast" MyISAM and very serious restrictions (like the one you've run into) or "slow", but relatively featured InnoDB. Whereas PgSQL tables are almost as fast as MyISAM (when I tested them myself, can't say what's with latest versions, PgSQL hit 8.4, for example, etc.) and have quite a lot of advanced features. And now you cannot just switch to PgSQL, not with your data and everything, that'd be awfully huge amount of work.
If we talk about replication, there's no replication support in core PgSQL (as far as I can remember), but there's several 3rd party packages for the purpose.
Charles SchlossChas4 # Wednesday, December 9, 2009 5:02:35 PM