We are happy to see that Percona Server/XtraDB and XtraBackup are raising popularity and to keep excitement we want to have more features and more performance fixes! If you are experienced software engineer and feel strong enough to hack InnoDB/XtraDB code we invite you to join our development team to work on the following (but not limited to) problems:
Recently at href="http://omniti.com/surge/2011" target="_blank">Surge 2011, the annual conference on scalability and performance, Google's CIO Ben Fried gave an illuminating href="http://www.eweek.com/c/a/Enterprise-Applications/Googles-CIO-Generalists-Not-Specialists-Will-Scale-the-Web-655875/" target="_blank">keynote address. His main insight was that generalists are the people that will lead engineering teams in successfully scaling the web.
Even if you didn’t make it to Percona Live London, you can get the chance to hang out with us.
We’re giving a reception at the Revolution Bar America Square just a few meters walk from the Tower Hill Underground between 17:30 and 19:30 today (Tuesday 25 October 2011).
All friends of Percona are welcome. See you there!
Thanks to Clustrix for sponsoring the drinks.
Percona Live London starts on Monday, so this is the last in the series of free-Percona-Live tickets we’ll give away. But first — have you ever wondered what servers are in your MySQL replication hierarchy?
Recently, someone emailed me:
I have a requirement in MYSQL as follows:
we have a table
EMPand we have to restrict the users not delete employees with
DEPT_ID = 10. If user executes a
DELETEstatement without giving any
WHEREcondition all the rows should be deleted except those with
DEPT_ID = 10.
We are trying to write a
BEFORE DELETE trigger but we are not able to get this functionality.
I'm having a lot of fun writing common_schema, an SQL project which includes views, tables and stored routines.
As the project grows (and it's taking some interesting directions, in my opinion) more dependencies are being introduced, and a change to one routine or view may affect many others. This is why I've turned the development on common_schema to be test driven.
Now, just how do you test drive an SQL project?
I am trying to understand why a server would go from 0 to 45 and then back to 0 seconds of replication lag as reported by the Seconds_Behind_Master column in SHOW SLAVE STATUS output. This occurs over a few seconds so there isn't a statement that runs for 45 seconds on the slave. I then compared consecutive SET TIMESTAMP values in the binlog and the absolute value of the differences is at most 2 seconds.
Blackhole tables are often used on a so-called “relay slave” where some operation needs to happen but no data needs to exist. This used to have a bug that prevented AUTO_INCREMENT columns from propagating the right values through replication, but that was fixed. It turns out there’s another bug, though, that has the same effect. This one is caused when there is an INSERT into a Blackhole table, where the source data is SELECT-ed from another Blackhole table.
For me, next week’s Percona Live is a lot like other events: I know I will be busy meeting and greeting and helping unpack boxes and so forth, but I’ll also be talking and attending other talks. With five concurrent tracks, it’s tough to decide. This is roughly the equivalent of the MySQL conference every year, which has more tracks, but historically it’s been easy to cross off some talks as sales pitches. Not so with this event! Here’s what I want to see the most:
|I will be a speaker at Percona Live - London 2011, and I am looking forward to the event, which is packed with great content.|