Join Web and Telecom companies who have adopted MySQL Cluster to facilitate application in the following areas:

Web:

• High volume OLTP
• eCommerce
• User profile management
• Session management and caching
• Content management
• On-line gaming

Telecoms:

• Subscriber databases (HLR/HSS)
• Service deliver platforms
• VAS: VoIP, IPTV and VoD
• Mobile content delivery
• Mobile payments
• LTE access

To come up to speed on MySQL Cluster, take the 3-day MySQL Cluster training course. Events already on the schedule include:

8PM. One of the servers found a critical bug. Hop online and discuss, log bug. 10PM. Patch ready. 10:30PM. New build ready. 10:45PM. New RQG run initiated. This was by no means an uncommon sight during the months of testing that went into Percona Server 5.6, in fact it was commonplace.

At a certain point, we had 3 very high end servers (modern cpu’s, heaps of cores and memory), all equipped with either fast SSD’s or Fusion-io flash storage, executing thousands of trials, 8 in parallel per server, each executing 1 to 25 mysql threads per running mysqld instance.

And that was just the final months of testing. Before that much work was done on finding “every last bug out there”. We discovered many bugs in both upstream (Oracle’s MySQL 5.6) and in Percona Server 5.6. I personally logged around 100 bugs, but the total count would be much higher still.

My colleague …

How do we ensure that, when we have 35+ testable option combinations for mysqld, we test each and every combination of them? For example: will a different innodb_log_file_size combined with more innodb_log_files_in_group and a modified innodb_fast_shutdown setting truly not affect Percona’s log archiving feature?

Most option-related bugs are caused by the setting of 1 or 2 mysqld options to a non-standard value. Maybe in an odd situation 3 mysqld options need to be set in combination. So, starting with 2 option combinations (1 option set is easy to calculate: it matches the number of options to be tested), let’s see how many combinations we would have to run: 35^2 = 1225 combinations. aa, ab, ac, …. ba, bb, bc… etc.

In real life mysqld testing, this is not entirely true as one would never specify “aa” in relation to …

This post builds on the How to obtain the “LES” (Last Executed Statement) from an Optimized Core Dump? post written about a year ago.

A day after that post was released, Shane Bester wrote an improved version, How to obtain all executing queries from a core file on his blog. Reading that post is key to understanding what follows.

I am faced with some complex bugs which would do well with SQL testcases. Extracting the last executed statement (and maybe all queries running at the time of the crash/asserts) is crucial to generate testcases well. E.g. you may have a full SQL trace from RQG or …

Me and some of my colleagues are giving MySQL talks at OSI days. Check out the schedule at http://osidays.com/osidays/open-source-india-day-3/. Hope to see you all there.

DB-Engines.com (http://db-engines.com/en/ranking/relational+dbms) ranks MySQL as the #2 most popular relational database after Oracle.  MySQL is continuing to grow and gain market share.   MySQL 5.6 and 5.7 show the database server is continuing to add significant new functionality in each release.  MySQL is extremely fast and scalable.  MySQL cluster can also perform well against the fastest

There is a new feature in the MariaDB 10 Beta which caught my eye: support for returning a result set on delete.

With a 'regular' DELETE operation you only get to know the number of affected rows. To get more info or actions you have to use a trigger or a foreign key. Anoter posibility is doing a SELECT and then a DELETE and with the correct transaction isolation a transactional support this will work.

With the support for the RETURNING keyword this has become easier to do and it will probably bennefit performance and save you a few roundtrips and a few lines of code.

There is already support for RETURNING in PostgreSQL. And PostgreSQL has an other nifty feature for which RETURNING really helps: CTE or common table expressions or the WITH keyword. I really hope to see CTE support in MySQL or MariaDB some day.

…

Attending Percona Live in London next week?

Don’t miss the chance to hear Tokutek’s Vice President of Engineering, Tim Callaghan, discuss how to use your MySQL knowledge to become an instant MongoDB Guru and the advantages of using Fractal Tree® indexes in MySQL and MongoDB. Tim will be speaking about these topics in two separate sessions at 12:00pm and 5:00pm on November 12.

For more information on these sessions and Percona Live-London, visit https://www.percona.com/live/london-2013/users/tim-callaghan.

The Colorado MySQL meetup is getting together on November 11th.

Location: Oracle 500 Eldorado Boulevard, Broomfield, CO

All MySQL users and interested parties are invited to participate and attend the following activities! 

Monday, November 11, 2013

From 6:00PM to 8:30PM

• Oracle Broomfield Office
  Building 1 – Demo 1127 Conference Room
  500 Eldorado Blvd
  Broomfield, CO 80021

  Schedule:
  6PM Meet, Greet, and Eat
  6:30-45 – Intro’s/Updates
  6:45-7:30 – Session 1 – MySQL 5.6 and Cluster Update – Lee Stigile, Oracle
  7:30-8:15 – Session 2 – MySQL and Hadoop Integration – Dave Smelker, ADURANT Technologies
  8:15-8:30 – Closing
  For further information, please contact:
  George Trujillo
  Email: [masked]
  Cell: [masked] …