Re: MySQL Community Server 5.1.35 has been released
On Thu, Jun 04, 2009 at 01:27:34PM -0600, Timothy Smith wrote: Dear MySQL users, MySQL Community Server 5.1.35, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.35 is recommended for use on production systems. For an overview of what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.35 on new servers or upgrading to MySQL 5.1.35 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-35.html Enjoy! Timothy Smith The MySQL build team at Sun Microsystems === This release of MySQL has two known outstanding issues for Windows: * The .msi installer does not detect an existing root password on the initial configuration attempt. To work around this, install and configure MySQL as normal, but skip any changes to security. (There is a checkbox that allows this on the security screen of the configuration wizard.) Then check your settings: + If the old root password and security settings are okay, you are done and can proceed to use MySQL. + Otherwise, reconfigure with the wizard and make any changes on the second configuration attempt. The wizard will properly prompt for the existing root password and allow changes to be made. This issue has been filed as Bug#45200: http://bugs.mysql.com/45200 for correction in a future release. * The Windows configuration wizard allows changes to InnoDB settings during a reconfiguration operation. For an upgrade, this may cause difficulties. To work around this, use one of the following alternatives: + Do not change InnoDB settings. + Copy files from the old InnoDB location to the new one. This issue has been filed as Bug#45201: http://bugs.mysql.com/45201 for correction in a future release. Bugs fixed: * Important Change: Replication: The transactional behavior of STOP SLAVE has changed. Formerly, it took effect immediately, even inside a transaction; now, it waits until the current replication event group (if any) has finished executing, or until the user issues a KILL QUERY or KILL CONNECTION statement. This was done in order to solve the problem encountered when replication was stopped while a nontransactional slave was replicating a transaction on the master. (It was impossible to roll back a mixed-engines transaction when one of the engines was nontransactional, which meant that the slave could not safely re-apply any transaction that had been interrupted by STOP SLAVE.) (Bug#319: http://bugs.mysql.com/319, Bug#38205: http://bugs.mysql.com/38205) See also Bug#43217: http://bugs.mysql.com/43217. * Partitioning: When a value was equal to a PARTITION ... VALUES LESS THAN (value) value other than MAXVALUE, the corresponding partition was not pruned. (Bug#42944: http://bugs.mysql.com/42944) * Replication: Unrelated errors occurring during the execution of RESET SLAVE could cause the slave to crash. (Bug#44179: http://bugs.mysql.com/44179) * Replication: The --slave-skip-errors option had no effect when using row-based logging format. (Bug#39393: http://bugs.mysql.com/39393) * Replication: The following erors were not correctly reported: + Failures during slave thread initialization + Failures while initializing the relay log position (immediately following the starting of the slave thread) + Failures while processing queries passed through the --init_slave option. Information about these types of failures can now be found in the output of SHOW SLAVE STATUS. (Bug#38197: http://bugs.mysql.com/38197) * Replication: Killing the thread executing a DDL statement, after it had finished its execution but before it had written the binlog event, caused the error code in the binlog event to be set
Re: high performance test data/test query generator
I usually simulate the load of the whole stack, by benchmarking the application directly using a tool such as jMeter. Loading MySQL specifically with read/write patterns similar to those of the real application can be useful, but quite hard to accomplish. One easy way of doing that is to enable logging in your server and capture the statements executed over a day or so, then extract the SQL statements into a separate file. You can use then use a tool such as mysqlslap (available since 5.1) to execute those statements in a number of iterations with a given concurrency on your benchmarking box. On Thu, Jun 4, 2009 at 2:05 PM, petya pe...@petya.org.hu wrote: Anyone else? You guys don't simulate realistic workload in benchmark just do sysbench or something like that? If there were a tool for that (which can handle data generation, initial database generation, and query generation, maybe it's output will be a jmeter test case) would you do so? Peter petya wrote: I use jmeter too, but it can't generate the test dataset (if I have to write this, I plan that it will create a jmeter test case with the generated test data). Usually my ad-hoc script generates csv files (to load initial data) and jmeter test cases. Michael Dykman wrote: On Wed, Jun 3, 2009 at 9:41 AM, petya pe...@petya.org.hu wrote: Hi, We have lots of mysql servers, master-slave and sharded databases. A recurring task when a new feature/application comes in to test the database with real workload. This needs test data and test query generation. Until now I did this with ad-hoc scripts, I looked for tools to do this, so far I found nothing. The closest thing to this was benerator, but it doesn't generate test queries. I need to measure write performance too (or concurrent read/write performance), so it would be good if I can tell the tool to generate bulk inserts with n records or generate a csv file or generate single insert... statements, so I can simulate the application's workload (of course I can do this with the application itself, but in development stage it is important to see how the database itself performs). Does such a tool exists? No problem if it is mysql only. If not, I think I will write one. Peter Boros It is by no means the only such tool, but I have often use JMeter as an all-purpose load-generation tool. It has good support for database testing among other things.. http://jakarta.apache.org/jmeter/usermanual/build-db-test-plan.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=amr.most...@gmail.com -- Amr Mostafa PHP Team Leader, Egypt Development Center amr.most...@egyptdc.comhttp://egyptdc.com +(2012)1700502 +(202)24052355/6
Re: high performance test data/test query generator
That only works if the application is already in production and gets a certain load. For a new application (for example the database is designed but the application is not ready yet) this doesn't work. Amr Mostafa wrote: I usually simulate the load of the whole stack, by benchmarking the application directly using a tool such as jMeter. Loading MySQL specifically with read/write patterns similar to those of the real application can be useful, but quite hard to accomplish. One easy way of doing that is to enable logging in your server and capture the statements executed over a day or so, then extract the SQL statements into a separate file. You can use then use a tool such as mysqlslap (available since 5.1) to execute those statements in a number of iterations with a given concurrency on your benchmarking box. On Thu, Jun 4, 2009 at 2:05 PM, petya pe...@petya.org.hu wrote: Anyone else? You guys don't simulate realistic workload in benchmark just do sysbench or something like that? If there were a tool for that (which can handle data generation, initial database generation, and query generation, maybe it's output will be a jmeter test case) would you do so? Peter petya wrote: I use jmeter too, but it can't generate the test dataset (if I have to write this, I plan that it will create a jmeter test case with the generated test data). Usually my ad-hoc script generates csv files (to load initial data) and jmeter test cases. Michael Dykman wrote: On Wed, Jun 3, 2009 at 9:41 AM, petya pe...@petya.org.hu wrote: Hi, We have lots of mysql servers, master-slave and sharded databases. A recurring task when a new feature/application comes in to test the database with real workload. This needs test data and test query generation. Until now I did this with ad-hoc scripts, I looked for tools to do this, so far I found nothing. The closest thing to this was benerator, but it doesn't generate test queries. I need to measure write performance too (or concurrent read/write performance), so it would be good if I can tell the tool to generate bulk inserts with n records or generate a csv file or generate single insert... statements, so I can simulate the application's workload (of course I can do this with the application itself, but in development stage it is important to see how the database itself performs). Does such a tool exists? No problem if it is mysql only. If not, I think I will write one. Peter Boros It is by no means the only such tool, but I have often use JMeter as an all-purpose load-generation tool. It has good support for database testing among other things.. http://jakarta.apache.org/jmeter/usermanual/build-db-test-plan.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=amr.most...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
