2. business software
  3. news
  4. reviews
  5. top apps
Download MySQL 5.1.70

MySQL 5.1.70

By MySQL AB  (Open Source)
User Rating

What Is the FileHippo Safety Guarantee?


We know how important it is to stay safe online so FileHippo is using virus scanning technology provided by Avira to help ensure that all downloads on FileHippo are safe. The program you are about to download is safe to be installed on your device.


# Bugs Fixed
- Important Change; Replication: When the server was running with --binlog-ignore-db and SELECT DATABASE() returned NULL (that is, there was no currently selected database), statements using fully qualified table names in dbname.tblname format were not written to the binary log. This was because the lack of a currently selected database in such cases was treated as a match for any possible ignore option rather than for no such option; this meant that these statements were always ignored. Now, if there is no current database, a statement using fully qualified table names is always written to the binary log.
- InnoDB: Valgrind testing returned memory leak errors which resulted from a regression . The dict_create_add_foreign_to_dictionary function would call pars_info_create but failed to call pars_info_free.
- InnoDB: The fix for resulted in a linker error.
- InnoDB: Crash recovery would fail with a !recv_no_log_write assertion when reading a page.
- Replication: Using the --replicate-* options (see Replication Slave Options and Variables) could in some cases lead to a memory leak on the slave.
- Replication: The binary log contents got corrupted sometimes, because the function MYSQL_BIN_LOG::write_cache always thought it had reached the end-of-cache when the function my_b_fill() reported a '0,' while that could also mean an error had occurred. This fix makes sure that whenever my_b_fill() returns a '0,' an error check is performed on info->error.
- The WKB reader for spatial operations could fail and cause a server exit.
- A GROUP_CONCAT() invocation containing subquery having an outer reference caused the server to exit.
- For debug builds, GROUP_CONCAT(... ORDER BY) within an ORDER BY clause could cause a server exit.
- If loose index scan was used on a query that used MIN(), a segmentation fault could occur.
- A prepared statement that used GROUP_CONCAT() and an ORDER BY clause that named multiple columns could cause the server to exit.
- ORDER BY MATCH ... AGAINST could cause a server exit.
- When a partition is missing, code in ha_innodb.cc would retry 10 times and sleep for a microsecond each time while holding LOCK_open. The retry logic for partitioned tables was introduced as a fix but did not include a test case to validate it. This fix removes the retry logic for partitioned tables. If the problem reported reappears, a different solution will be explored.
- The mysql.server script exited with an error if the status command was executed with multiple servers running.
- When processing row-based-replication events in the old binary log format from prior to MySQL 5.1 GA builds, mysqlbinlog could result in out-of-bounds heap buffer reads and undefined behaviour.
- The mysql client allocated but did not free a string after reading each line in interactive mode, resulting in a memory leak.
- Grouping by an outer BLOB column in a subquery caused a server exit.
- The url columns in the mysql datatbase help tables were too short to hold some of the URLs in the help content. For new installations, these columns are now created as type TEXT to accommodate longer URLs.
- For upgrades, mysql_upgrade does not update the columns. Modify them manually using these statements:
ALTER TABLE mysql.help_category MODIFY url TEXT NOT NULL;
ALTER TABLE mysql.help_topic MODIFY url TEXT NOT NULL;
- The test for stack overrun did not work for recent gcc versions and could lead to server exit.
- IF() function evaluations could produce different results when executed in a prepared versus nonprepared statement.