The latest from the MySQL community

Everything is available at the project page

Please report issues and feature request here.

Version 0.2 is a bug fix release but with 2 significant changes in syntax:

1. Changed all constructor methods from create(...) to new. Seems to be more common in the LUA world.
2. The logger class is now returned by the module. So it is local logger = require("optivo.common.log4lua.logger")
   local LOG = logger.new(…)

   instead of

   local logger = require("optivo.common.log4lua.logger")
   local LOG = logger.Logger.create(…)

Some potential bugs have been spotted using (a slightly adopted version of) lualint and …

How is the newest browser fairing in technical reviews? READ MORE

We made new patches, improved previous and want to announce new builds for 5.0.62, 5.0.67 and 5.1.26 versions. One of biggest changes we separated releases of 5.0 into two branches.
First, just "-percona" release is more stable and contains only stable and proven on many installation patches. Second is "-percona-highperf" release, which contains experimental patches that can improve performance significantly. On this stage "percona-highperf" contains patches from Yasufumi Kinoshita (more info on Maximum performance of OLTP benchmark is not so scalable on multi-cpu.
Most important patch "split_buf_pool_mutex" to separate InnoDB buffer->pool mutex into several, and it allows to get 1.5x - 2.5x improvements in DBT2 benchmarks on 8cores boxes (benchmark results is coming and will be published)

For all three versions we added SHOW PATCHES command, which is based …

Mark Schoonover has asked me to take over the LinkedIn Group for MySQL Certified Professionals. We are still working out the details but I would like to ask the almost 200 members of that group and any potentially interested others what they would like to see this professional community become.

Personally, I am going to need a platoon of MySQL Exam beta test guinea pigs and this group looks like a great source for talent people.

But what do the members want?

Cisco gives accounts with CCIEs on staff a percentage discount on support contracts? They also get an escallated queue for any support calls. The logic behind that is that a CCIE would not call on something trival and would have triaged the problem. Is this something for this group?

Or do we need t-shirts? Mugs? A special room (rubber padded, drool absorbant carpet) reserved for us at the 2009 Users Conference?

What …

This is the 113th edition of Log Buffer, the weekly review of database blogs.

Sheeri Cabral gets things going this week with her coverage of this rumour: Monty Widenius Leaves Sun/MySQL. If it turns out to be true, that seems like bad–or at least sad–news for MySQL, but Sheeri’s take is mostly an optimistic one.

MySQL’s Kaj Arno responds to the rumours on Monty resigning: “First, it’s a rumour.  . . .  Second, Monty’s resignation has been a possible outcome already since years before the Sun …

I would like to make this post to reference one of posts published on mysql.com website. A lot of mysql users visit our site and I think our users will be willing to help. Here are the full details:

Donations are requested to help Andrii Nikitin, a MySQL support engineer in Ukraine, provide for his son Ivan who requires a bone marrow transplant operation. The cost of this operation is expected to be between €150,000 - €250,000 ($235,000 - $400,000). Please help us provide Ivan a chance to live.

More information can be found here: http://www.mysql.com/about/help-ivan.html

Slave delay can be a nightmare. I battle it every day and know plenty of people who curse the serialization problem of replication. For those who are not familiar with it, replication on MySQL slaves runs commands in series – one by one, while the master may run them in parallel. This fact usually causes bottlenecks. Consider these 2 examples:

• Between 1 and 100 UPDATE queries are constantly running on the master in parallel. If the slave IO is only fast enough to handle 50 of them without lagging, as soon as 51 start running, the slaves starts to lag.
• A more common problem is when one query takes an hour to run (let's say, it's an UPDATE with a big WHERE clause that doesn't use an index). In this case, the query runs on the master for an hour, which isn't a big problem because it doesn't block other queries. However, when the query moves over to the slaves, all of them start to lag because it plugs up the single …

Some weeks ago there was a request about adding a feature that keeps (or gets) datatypes of colums, which are connected via foreign keys, in sync. While we have added this to our ToDo list, I thought of doing some simple LUA exercises to give the user at least a funtion to check if the FKs in the model all have columns with matching datatypes.
As it turned out such tasks can be done quite easily using our GRT-shell. And by writing some functions you can add features to Workbenchs interface.

To get in touch with the shell/GRT environment inside Workbench click the tiny black prompt-window-icon in the top right area of workbench (or choose ‘View->Advanced->GRT Shell’ from the main menu).  Some items in the UI are swapped/added: the sidebar on the right side gets a new tab named ‘GRT Shell’ featuring some more tool-panes (GRT Tree, Modules, Inspector) and on the bottom part of the main window - where the editors …

As you may have noticed we’re going for a major milestone on our Workbench 5.1 roadmap. So our resources are pretty much concentrated on this  task at the moment. But it’s just as important to keep improving our 5.0 GA version, so we will reserve the first days next week to make progress here as well. We will publish the next release of 5.0 mid-next-week. So stay tuned for a better 5.0 next week and the upcoming 5.1 alpha later this month.

Valleywag reports that Monty Widenius has quit Sun. The Pythian Group reckons its true. Kaj Arno’s non-denial denial would appear to confirm it despite his protestations otherwise.

“Technically there is no resignation letter. However, I spoke to Monty yesterday, and yes, resignation is an option he considers,” writes Kaj before expanding on some of the reasons that Monty might consider leaving Sun and how the MySQL project would continue without him (or without him as an employee at any rate).

He concludes: “In summary, I can neither confirm nor deny the rumour. But I hope my posting has shed some light on the …