Version 5.0.90 marks the end of active development for the 5.0 series, and the approach of its official end of life. From this point on, only severity 1 security fixes will be available from upstream. Due to this we will be making the transition to 5.1 in the atomic repository.
Changelog: * Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us with a proof-of-concept script that allowed us to reproduce this bug. (Bug#50227, CVE-2009-4484) * Replication: FLUSH LOGS did not actually close and reopen the binary log index file. (Bug#48738) See also Bug#34582. * Some prepared statements could raise an assertion when re-executed. (Bug#49570) * Valgrind warnings for CHECKSUM TABLE were corrected. (Bug#49465) * Specifying an index algorithm (such as BTREE) for SPATIAL or FULLTEXT indexes caused a server crash. These index types do not support algorithm specification, and it is now disallowed to do so. (Bug#49250) * The optimizer sometimes incorrectly handled conditions of the form WHERE col_name='const1' AND col_name='const2'. (Bug#49199) * Several strmake() calls had an incorrect length argument (too large by one). (Bug#48983) * On Fedora 12, strmov() did not guarantee correct operation for overlapping source and destination buffer. Calls were fixed to use an overlap-safe version instead. (Bug#48866) * Incomplete reset of internal TABLE structures could cause a crash with eq_ref table access in subqueries. (Bug#48709) * Re-execution of a prepared statement could cause a server crash. (Bug#48508) * The error message for ER_UPDATE_INFO was subject to buffer overflow or truncation. (Bug#48500) * On Solaris, no stack trace was printed to the error log after a crash. (Bug#47391) * Comparison with NULL values sometimes did not produce a correct result. (Bug#42760) * When compressed MyISAM files were opened, they were always memory mapped, sometimes causing memory-swapping problems. To deal with this, a new system variable, myisam_mmap_size, was added to limit the amount of memory used for memory mapping of MyISAM files. (Bug#37408)
Users browsing this forum: No registered users and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum