Comments on: Raj’s MySQL Top Five Wishlist

By: Raj Thukral

Raj Thukral — Thu, 12 Jul 2007 13:40:35 +0000

Looks like this blog post has received a lot of attention / comments.

While I never intended it to be more than a quick-list, I guess my part-oracle background does show through, and there is a lot of stuff here that requires clarification

Rather than replying to each post, I think I’m going to write up a separate post about each of the 5 items in my wishlist in more detail, with real-world examples based on issues I’ve faced and how I would have liked to resolve them.

In short though, for #5 yes, I’m looking for something more restrictive than what MySQL currently provides. for #1 and #3, I’m looking at how I can quickly get to the root of problems in Oracle by looking at the metrics (wait events, locks etc.) that Oracle provides which I find sorely missing in MySQL..

Details to come.
–Raj.

By: Sheeri

Sheeri — Thu, 12 Jul 2007 00:49:09 +0000

Could you give more specific examples of #1 and #3, perhaps from other RDBMS’s? It would probably be 2 posts…but I think it would be really helpful for folks who don’t even realize what they need….

By: Xaprb

Xaprb — Wed, 11 Jul 2007 17:38:13 +0000

Your list has a couple items I’ve worked to address with innotop and mysqltoolkit. Still, there is no substitute for something the server implements itself; that will be much better than anything I can do with scripts.

By: Harrison Fisk

Harrison Fisk — Wed, 11 Jul 2007 15:56:34 +0000

As for your #5, there is already a read_only setting which will only allow two people to change data, the SQL thread in replication, and anyone with the SUPER privilege. As long as you don’t give your developers SUPER, then it will work exactly how you want.

SET global read_only = 1;

By: hartmut holzgraefe

hartmut holzgraefe — Wed, 11 Jul 2007 15:50:02 +0000

#5 is already there? http://dev.mysql.com/doc/refman/5.0/en/replication-options.html#option_mysqld_read-only

Or do you want this to be even more restricted?