…>2; Query OK, 9 rows affected (0.00 sec) mysql> select * from am; +—–+ | i | +—–+ | 2 | | 3 | | 5 | | 10 | | 100 | | 101 | | 102 | | 103 | | 104 | | 105 | +—–+ 10 rows in set (0.00 sec) mysql> select * from… run flush tables. I’ve done my tests with MySQL 5.0.62.
… pair (c,i) looks a bit off but is within 0.5% of the correct value so we can count on MyISAM… OK, 245760 rows affected (54.29 sec) Records: 245760 Duplicates: 0 Warnings: 0 mysql> show index from antest_innodb; +—————+————+———-+————–+————-+———–+————-+———-+——–+——+————+———+ | Table | Non_unique… from reality too. MySQL version note: This is from MySQL 5.0.62 if there are other versions which show different behavior.
Dmitry, MySQL 5.0 is the latest stable “GA” release (5.1 is still RC) this is why I focus on … unlike with 4.0 for example there were MySQL 5.0 release coming out during these months. There is MySQL 5.0.62 however there all…
There is patch for 5.0.62 http://www.mysqlperformanceblog.com/mysql-patches/ We also have patch in work for 5.0.67 If you need patch for 5.0.61 or any other version we can do backport on consulting basics.
I installed the 5.0.75-build11 binaries. And it works great, only that I would not want error logging in syslog. Is there a way to disable it without compiling from sources without mysqld_safe_syslog-5.0.62.patch? I am using mysqld_multi script to start the instance. Thanks
… users are not rushing to upgrade to latest and greatest 5.0.62 This means MySQL Enterprise versions are lesser tested and so… now at large extent wasted – MySQL can little gain from 5.0.51 bug reports because many of them are fixed in…
….user_statistics along with show user_statistics. Links: Patch for 5.0.62 Patch for 5.1.26
… *** Error code 1 Stop in /usr/mace/mysql/unp/mysql-5.0.62-percona/sql. *** Error code 1
Have you applied the patches to the 5.0.62 source? “Reversed (or previously applied) patch detected! Assume -R?”
Funny. I just noticed the link above for 5.0.62 is a patch.