The binary version for MySQL Cluster 7.0.13 has now been made available at http://dev.mysql.com/downloads/cluster/ under the GA tab.
A description of all of the changes (fixes) that have gone into MySQL Cluster 7.0.13 (compared to 7.0.12) can be found in the MySQL Cluster 7.0.13 Change Log.
Using the Embedded InnoDB plugin I’m working on, you can use the INNODB_STATUS table function in the data_dictionary, you can do pretty neat things.
For example, we can see that each autocommit transaction causes an fsync and if you insert multiple rows ina single statement, you still only get 1 fsync:
drizzle> SELECT * FROM DATA_DICTIONARY.INNODB_STATUS
-> WHERE name="fsync_req_done";
+----------------+-------+
| NAME | VALUE |
+----------------+-------+
| fsync_req_done | 25 |
+----------------+-------+
1 row in set (0 sec)
drizzle> insert into t1 values (1);
Query OK, 1 row affected (0.05 sec)
drizzle> SELECT * FROM DATA_DICTIONARY.INNODB_STATUS WHERE name="fsync_req_done";
+----------------+-------+
| NAME | VALUE |
+----------------+-------+
| fsync_req_done | 26 |
+----------------+-------+
1 row in set (0 sec)
drizzle> insert into t1 values (1),(2),(3),(4);Query OK, 4 rows affected (0 …[Read more]
I am rather excited about being able to do awesome things such as this to get the current configuration of your server:
drizzle> SELECT NAME,VALUE
-> FROM DATA_DICTIONARY.INNODB_CONFIGURATION
-> WHERE NAME IN ("data_file_path", "data_home_dir");
+----------------+-------+
| NAME | VALUE |
+----------------+-------+
| data_file_path | NULL |
| data_home_dir | ./ |
+----------------+-------+
2 rows in set (0 sec)
drizzle> SELECT NAME,VALUE
-> FROM DATA_DICTIONARY.INNODB_CONFIGURATION
-> WHERE NAME IN ("data_file_path", "data_home_dir");
+----------------+-------+
| NAME | VALUE |
+----------------+-------+
| data_file_path | NULL |
| data_home_dir | ./ |
+----------------+-------+
2 rows in set (0 sec)
drizzle> SELECT NAME,VALUE
-> FROM DATA_DICTIONARY.INNODB_CONFIGURATION
-> WHERE NAME = "io_capacity";
+-------------+-------+
| NAME | VALUE | …[Read more]
We have an early draft of a new tool available for you to use and test. It uses heuristics to find problems in SQL. Please use it and give feedback! Here’s how: $ wget http://www.maatkit.org/trunk/mk-query-advisor $ perl mk-query-advisor /var/log/mysql/slow.log By default it consumes a log file in MySQL’s slow query log format, but it can also parse the general-log format, and if you have any other kind of log you can feed it through mk-query-digest to transform the log into something it can recognize.
Many Percona employees will be at the 2010 MySQL conference. We'll be giving a lot of informative technical talks on various topics. Here's a list:
Dear MySQL Community
I would like to ask for your help as I am writing a report for
use cases for denormalization.
Could you please add a comment if you have used denormalization
in the past to help solve a certain problem. If you could add
what was the problem, how did you apply denormalization and how
effective (or not) was it?
Thank you in advance.
5 months more...
reminder, what is Dbspj:
- It's a new feature for MySQL Cluster
- It gives the possibility to push-down SQL joins, i.e to
evaluate the joins inside the data nodes.
latest and greatest:
- last 5 months spent on SQL integration
- big effort having it used only for cases that we actually
support
- lots of testing using RQG
- a significant part of bugs found last couple weeks, has
not been related to spj, but in fact "ordinary" optimizer
bugs
- we think that it's quite usable now.
and the numbers:
- my plan was to present TPC-W as "realistic" numbers
- now they look more like fantastic numbers
- if i could, i would add a "25x" to my title
- visit my UC presentation ( …
Dear Community,
We are announcing today the new version 9.1 of XtraDB storage engine.
The name of binaries has changed to Percona-XtraDB. It is applicable to all packages including RPM, DEB and tar.gz packages.
New features in version 9.1:
In our first alpha of InfiniDB 1.1, we’ve responded to a number of feedback items from our community, and we’d like to thank those of you who have been working with us on these and other things. Specifically, two recurring comments from the community, with respect to our 1.0 version, were: (1) CREATE TABLE statements for wide tables sometimes take a long time to complete; (2) The amount of space used by empty and/or small tables is excessive.
First, a little background as tRead More...
During the MySQL conference Call for Papers there was some
talk of getting one or two Postgres sessions into the mix, as a lot of MySQL
users seem to have questions about Postgres these days. Alas,
looking through the MySQLcon schedule I don't see any on there.
I've also looked through the BOF's and nothing about Postgres to
be found there either. So, maybe no one is interested in Postgres
after all.
However I held a Postgres BOF at MySQLcon last year and we got a
handful of people, and since I am going to be at MySQLcon again
this year, I might as well host one again. I think it's too late
to schedule one formally, but I can put some info on the schedule
sheets once I'm at the conference; if you are interested in
learning some more about Postgres, please keep an eye out.