PlanetMysql.ru — информация о СУБД MySQL

Following closely on the heels of the MariaDB 5.3.4-rc release a couple of weeks ago, the MariaDB project is pleased to announce the immediate availability of MariaDB 5.3.5!

MariaDB 5.3.5 is the first stable (GA) release in the 5.3 series. Details and downloads are available from the following links:

• MariaDB 5.3.5 Release Notes
• MariaDB 5.3.5 Changelog
• MariaDB 5.3.5 Downloads

(Debian and Ubuntu packages are available from our mirrored apt repositories. A sources.list generator is available.)

About MariaDB 5.3

The MariaDB 5.3 series introduces many new features, includes MariaDB
5.2, and is based on MariaDB 5.1 & MySQL 5.1. Some highlights of new
features in MariaDB 5.3 include:

• subquery optimizations that finally make subqueries usable
• many optimizer changes, including Classic Hash Join, Batched Key Access, a new implementation of Multi-Range-Read optimizations as well as Index Condition Pushdown
• NoSQL-style interfaces via the HandlerSocket plugin as well as dynamic columns
• group commit in XtraDB when the binary log is enabled
• Microsoft Windows performance improvements

These are just some of the highlights, and for a more complete list of changes, please see the What is MariaDB 5.3 page.

PlanetMySQL Voting: Vote UP / Vote DOWN

We’re excited to announce that customers & users of Continuent will now receive our expert MySQL™ database solutions, services and support when they use Continuent’s Tungsten Enterprise, a complete clustering and data management solution for the MySQL database. The same applies to customers using Tungsten Replicator, an advanced data replication solution.

Overall, the big news is that our companies will now jointly offer Tungsten Enterprise and Tungsten Replicator-based solutions to help MySQL users in accelerating the deployment and management of clustered MySQL databases, as well as the deployment of complex data replication solutions. We will also together offer MySQL users the SkySQL Enterprise subscription, a comprehensive offering of server software, production support and monitoring tools for any version of the MySQL database.

SkySQL continues to be focused on bringing the MySQL database into the future while providing expert support and services to those using the database today, and this is another strong step in that direction.

For more information on our combined solution, visit our site or Continuent's .

PlanetMySQL Voting: Vote UP / Vote DOWN

Continuent and SkySQL announced today a strategic partnership. SkySQL will provide its expert MySQL database software, services and support to customers of Continuent’s Tungsten Enterprise, a complete clustering and data management solution for MySQL, and Tungsten Replicator, an advanced data replication solution.Under the partnership agreement, SkySQL and Continuent will jointly offer Tungsten
PlanetMySQL Voting: Vote UP / Vote DOWN

mysql> CREATE TABLE t1 (id INT PRIMARY KEY ) 
             engine=myisam PARTITION BY HASH(id) PARTITIONS 1000;
Query OK, 0 rows affected (0.18 sec)

mysql> alter table t1 add column v int;
ERROR 1016 (HY000): Can't open file: './test/t1.frm' (errno: 24)

mysql> quit
Bye

$ perror 24
OS error code  24:  Too many open files

Looks as if MyISAM tries to open all the 1000 partition .MYD/.MYI files at once and runs out of file handles during this operation ...

PlanetMySQL Voting: Vote UP / Vote DOWN

Creating or dropping a partitioned table on InnoDB can become a quite expensive operation, on my laptop i'm seeing the following times for a simple table with 100 or 1000 partitions (using 5.1.58 right now as i'm testing on stock Ubuntu 11.10):

  mysql> CREATE TABLE t1 (id INT PRIMARY KEY )
               engine=innodb PARTITION BY HASH(id) PARTITIONS 100;
  Query OK, 0 rows affected (5.21 sec)

  mysql> drop table t1;
  Query OK, 0 rows affected (5.11 sec)

  mysql> CREATE TABLE t1 (id INT PRIMARY KEY )
               engine=innodb PARTITION BY HASH(id) PARTITIONS 1000;
  Query OK, 0 rows affected (52.76 sec)

So the time to create a partitioned InnoDB table grows linearly with the number of partitions at a 'speed' of about 20 partitions per second, and during that time the hard disk LED is always on. The rate for creating regular InnoDB tables on this machine is about 10 tables per second by the way.

MyIsam on the other had can create around 17 tables per second, and creating a single partitioned MyISAM table only takes about a 10th of a second.

So what is going on with InnoDB here? First of all from the engines point of view each partition of a partitioned table is an actual table, all the partitioning magic happens on a layer above the storage engine one, and the storage engine only receives handler requests for the actual partition tables involved. On the storage engine layer the actual engines are not aware that these tables are part of a larger partitioned table at all (with the exception of ndbcluster tables, but MySQL Cluster is a different story in this respect anyway).

So when creating an InnoDB table with 1000 partitions the InnoDB storage engine actually receives 1000 individual requests to create a table. Now what seems to happen is that for each
created partition/table InnoDB flushes at least its internal data dictionary to disk. Given the constant disk activity and rather low internal table creation rate it may even do a full checkpoint for each table, i haven't checked the details on this yet. And when dropping a partitioned table the same thing happens in reverse.

So this may be something to keep in mind when planning to use large numbers of partitions on InnoDB ...

PlanetMySQL Voting: Vote UP / Vote DOWN

Last week I was part of a discussion panel on SQL versus NoSQL. Many in the audience seemed to believe that you needed to be one or the other with an exclusive or. Then today I learned about Vitess, an idea to use MySQL as a data layer while providing easy scaling and control the roll out of a logical schema. Is there room for an inclusive or.

Some traditional SQL rules are relaxed in conjunction with pools of sessionless connections. I hope Vitess does well and maybe this hybrid approach makes some of our current SQL/NoSQL arguments moot.

PlanetMySQL Voting: Vote UP / Vote DOWN

MySQL Tech Tour Event – CO Springs
Monday, March 12, 2012
1:00 PM – 4:30 PM
Invite:
http://www.oracle.com/us/dm/sev100051614-wwmk11042736mpp146-1526263.html

MySQL Tech Tour Event – San Diego
Wednesday, March 14, 2012
1:00 PM – 4:30 PM
Invite:
http://www.oracle.com/us/dm/h2fy11/51630-wwmk11042736mpp145c003-oem-1526730.html

MySQL Tech Tour Event – Phoenix
Friday, March 16, 2012
1:00 PM – 4:30 PM
Invite:
http://www.oracle.com/us/dm/h2fy11/51928-wwmk11042736mpp142c004-oem-1526740.html

MySQL OEM Tech Tour – Burlington
Higher Application Performance and Streamlined Development with MySQL Embedded
Wednesday, March 14, 2012
9:00 AM – 12:30 PM
Invite:
http://www.oracle.com/us/dm/sev100052338-wwmk11042754mpp030-1529085.html

MySQL OEM Tech Tour – Reston
Higher Application Performance and Streamlined Development with MySQL Embedded
Tuesday, March 20, 2012
10:00 a.m. – 2:00 p.m.
Invite:
http://www.oracle.com/us/dm/h2fy11/51124-wwmk11042754mpp028c001-oem-1527057.html

PlanetMySQL Voting: Vote UP / Vote DOWN

MySQL Tech Tour Event – CO Springs
Monday, March 12, 2012
1:00 PM – 4:30 PM
Invite:
http://www.oracle.com/us/dm/sev100051614-wwmk11042736mpp146-1526263.html

MySQL Tech Tour Event – San Diego
Wednesday, March 14, 2012
1:00 PM – 4:30 PM
Invite:
http://www.oracle.com/us/dm/h2fy11/51630-wwmk11042736mpp145c003-oem-1526730.html

MySQL Tech Tour Event – Phoenix
Friday, March 16, 2012
1:00 PM – 4:30 PM
Invite:
http://www.oracle.com/us/dm/h2fy11/51928-wwmk11042736mpp142c004-oem-1526740.html

MySQL OEM Tech Tour – Burlington
Higher Application Performance and Streamlined Development with MySQL Embedded
Wednesday, March 14, 2012
9:00 AM – 12:30 PM
Invite:
http://www.oracle.com/us/dm/sev100052338-wwmk11042754mpp030-1529085.html

MySQL OEM Tech Tour – Reston
Higher Application Performance and Streamlined Development with MySQL Embedded
Tuesday, March 20, 2012
10:00 a.m. – 2:00 p.m.
Invite:
http://www.oracle.com/us/dm/h2fy11/51124-wwmk11042754mpp028c001-oem-1527057.html

PlanetMySQL Voting: Vote UP / Vote DOWN

The 2012 SouthEast LinuxFest registration and call for papers are now live on their site.

MySQL Days at SELF!

"This year we are specifically seeking speakers from all over the database spectrum for Open Database Camp. ODC at SELF will consist of a track of database talks selected by SELF on Saturday, then an unconference on Sunday. So if you have a database related talk, please submit!" -- RFP Form 
PlanetMySQL Voting: Vote UP / Vote DOWN

The 2012 SouthEast LinuxFest registration and call for papers are now live on their site.

MySQL Days at SELF!

"This year we are specifically seeking speakers from all over the database spectrum for Open Database Camp. ODC at SELF will consist of a track of database talks selected by SELF on Saturday, then an unconference on Sunday. So if you have a database related talk, please submit!" -- RFP Form 
PlanetMySQL Voting: Vote UP / Vote DOWN