Comments on: MySQL 5.1 Mix Of Handlers In Partitions http://venublog.com/2009/03/16/mysql-51-mix-of-handlers-in-partitions/ Everything In Life Is Random! (Personal and Work) Fri, 03 Sep 2010 17:25:38 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: James Day http://venublog.com/2009/03/16/mysql-51-mix-of-handlers-in-partitions/comment-page-1/#comment-9420 James Day Tue, 19 Jan 2010 11:49:38 +0000 http://venublog.com/?p=359#comment-9420 The stats for partitioned tables for all engines were being calculated based on only the first partition. That's now fixed in 5.1.41 and later: http://bugs.mysql.com/bug.php?id=44059 For InnoDB there was a bug in the 64 bit server index dive algorithm that caused it not to use truly random dives. Set innodb_use_legacy_cardinality_algorithm = 0 to turn off compatibility and turn on the more truly random fixed method. This bug fix: http://bugs.mysql.com/bug.php?id=43660 For partitioning in general, get a recent build like 5.1.43 when it's released soon. Lots of partitioning bug fixes since March 2009. The stats for partitioned tables for all engines were being calculated based on only the first partition. That’s now fixed in 5.1.41 and later:

http://bugs.mysql.com/bug.php?id=44059

For InnoDB there was a bug in the 64 bit server index dive algorithm that caused it not to use truly random dives. Set innodb_use_legacy_cardinality_algorithm = 0 to turn off compatibility and turn on the more truly random fixed method. This bug fix:

http://bugs.mysql.com/bug.php?id=43660

For partitioning in general, get a recent build like 5.1.43 when it’s released soon. Lots of partitioning bug fixes since March 2009.

]]> By: Pythian Group - Blog http://venublog.com/2009/03/16/mysql-51-mix-of-handlers-in-partitions/comment-page-1/#comment-5245 Pythian Group - Blog Fri, 20 Mar 2009 16:41:29 +0000 http://venublog.com/?p=359#comment-5245 [...] Venu Anuganti was also on the trail of partitions. He examined MySQL’s 5.1 Mix Of Handlers In Partition. [...] [...] Venu Anuganti was also on the trail of partitions. He examined MySQL’s 5.1 Mix Of Handlers In Partition. [...]

]]> By: Giuseppe Maxia http://venublog.com/2009/03/16/mysql-51-mix-of-handlers-in-partitions/comment-page-1/#comment-4953 Giuseppe Maxia Mon, 16 Mar 2009 22:12:34 +0000 http://venublog.com/?p=359#comment-4953 Don't hold your breath. Mix of handlers is not in the immediate plans, AFAIK. If you think it's a desirable feature, feel free to propose a patch, though. In the meantime, if you need to deal with short partitions on recent data and long partitions on historical data, you can create partitions of variable length. Yearly partitions for the old data, monthly partitions for the recent data. Giuseppe Don’t hold your breath. Mix of handlers is not in the immediate plans, AFAIK.
If you think it’s a desirable feature, feel free to propose a patch, though.

In the meantime, if you need to deal with short partitions on recent data and long partitions on historical data, you can create partitions of variable length. Yearly partitions for the old data, monthly partitions for the recent data.

Giuseppe

]]> By: rick http://venublog.com/2009/03/16/mysql-51-mix-of-handlers-in-partitions/comment-page-1/#comment-4947 rick Mon, 16 Mar 2009 19:39:19 +0000 http://venublog.com/?p=359#comment-4947 We started using partitions since 6 months in production and we had a table with logging of information for last few years and current month with inserts, updates.. and we left with choosing InnoDB at this time.. but once MySQL supports mix of handles; then old tables will be MyISAM and current active partition will be InnoDB We started using partitions since 6 months in production and we had a table with logging of information for last few years and current month with inserts, updates.. and we left with choosing InnoDB at this time.. but once MySQL supports mix of handles; then old tables will be MyISAM and current active partition will be InnoDB

]]>