De ontwikkelaars van MySQL hebben op hun forum een nieuwe versie van het programma aangekondigd. Het gaat om versie 5.0.20a die vanaf deze pagina in verschillende uitvoeringen voor een groot aantal platformen gedownload kan worden, waaronder OpenBSD, FreeBSD, diverse Linux-achtige platformen, Windows en Mac OS X. MySQL is een krachtige opensourcedatabaseserver die met name populair is als website- en forumdatabase. Tweakers.net maakt gebruik van MySQL om onder meer gebruikersgegevens, statistieken en diverse review-, meuk- en nieuwsartikelen in op te slaan. Afgelopen week hebben we een review online gezet waarin we de prestaties van onder meer MySQL 4.x en MySQL 5.x getest hebben op servers die uitgerust zijn met diverse AMD Opteron- en Intel Xeon-processors. De release notes van de nieuwbakken 5.0.20a-release ziet er als volgt uit:
Changes from 5.0.20 to 5.0.20a:
Additional information about SSL support:
- The fix for "Command line options are ignored for mysql client" (Bug #16855 (http://bugs.mysql.com/16855)) has been revoked, because it had introduced an incompatible change in the way the command line client ("mysql") selects the server to connect to. In the worst case, this might have led to a client issuing commands to a server for which they were not intended, and this must not happen. To help all users in understanding this subject, the manual now includes additional explanations in the section "4.2. Invoking MySQL Programs" (http://dev.mysql.com/doc/refman/5.0/en/invoking-programs.html)
- The code of the "yaSSL" library has been improved to avoid the dependency on a C++ runtime library, so a link with pure C applications is now possible on further (but not all) platforms. We are trying to fix the remaining issues.
Functionality added or changed in 5.0.20, but missing in previous announcement:
- With version 5.0.20a, SSL support is contained in all binaries for all Unix (including Linux) and Windows platforms except AIX, HP-UX, OpenServer 6, and the RPMs specific for RHAS3/RHAS4/SLES9 on Itanium CPUs ("ia64"); it is also not contained in those for Novell Netware. We are trying to add these platforms in future versions.
- Please note that the original 5.0.20 announcement included inexact wording, I am sorry for that and hope it did not cause too many searches: SSL support is "included" in both server and client, but by default not "enabled" - this can be done by passing the SSL-related options ("--ssl --ssl-key=... --ssl-cert=... --ssl-ca=...") when starting the server and the client or by setting these options in the config file. More information is in section "5.9.7. Using Secure Connections" (http://dev.mysql.com/doc/refman/5.0/en/secure-connections.html) of the manual.
Bugs fixed in 5.0.20, but missing in previous announcement:
- Added the --sysdate-is-now option to mysqld to enable SYSDATE() to be treated as an alias for NOW(). See Section 12.5, "Date and Time Functions." (Bug#15101 (http://bugs.mysql.com/15101))
- Large file support added to build for QNX platform. (Bug#17336 (http://bugs.mysql.com/17336))
- Large file support was re-enabled for the MySQL server binary for the AIX 5.2 platform. (Bug#13571 (http://bugs.mysql.com/13571), also listed as fixed Bug#10776 (http://bugs.mysql.com/10776))
- If the WHERE condition of a query contained an OR-ed FALSE term, the set of tables whose rows cannot serve for null-complements in outer joins was determined incorrectly. This resulted in blocking possible conversions of outer joins into joins by the optimizer for such queries. (Bug#17164 (http://bugs.mysql.com/17164))
- mysql_config returned incorrect libraries on x86_64 systems. (Bug#13158 (http://bugs.mysql.com/13158))
- Stored routine names longer than 64 characters were silently truncated. Now the limit is properly enforced and an error occurs. (Bug#17015 (http://bugs.mysql.com/17015))
- During conversion from one character set to ucs2, multi-byte characters with no ucs2 equivalent were converted to multiple characters, rather than to 0x003F QUESTION MARK. (Bug#15375 (http://bugs.mysql.com/15375))
- The mysql_close() C API function leaked handles for shared-memory connections on Windows. (Bug#15846 (http://bugs.mysql.com/15846))
- If InnoDB ran out of buffer space for row locks and adaptive hashes, the server would crash. Now InnoDB rolls back the transaction. (Bug#18238 (http://bugs.mysql.com/18238))
- InnoDB tables with an adaptive hash blocked other queries during CHECK TABLE statements while the entire hash was checked. This could be a long time for a large hash. (Bug#17126 (http://bugs.mysql.com/17126))
- For InnoDB tables created in MySQL 4.1 or earlier, or created in 5.0 or later with compact format, updating a row so that a long column is updated or the length of some column changes, InnoDB later would fail to reclaim the BLOB storage space if the row was deleted. (Bug#18252 (http://bugs.mysql.com/18252))
- InnoDB had a memory leak for duplicate-key errors with tables having 90 columns or more. (Bug#18384 (http://bugs.mysql.com/18384))
Database testopstelling: Dell PowerEdge 1850 met acht Raptor-schijven