Oracle ha rilasciato una nuova versione del suo RDBMS MySQL

MySQL 5.5.27 is a new version of the 5.5 production release ofthe world's most popular open source database. MySQL 5.5.27 is recommended for use on production systems.
MySQL 5.5 includes several high-impact enhancements to improve the performance and scalability of the MySQL Database, taking advantage of the latest multi-CPU and multi-core hardware and operating systems. In addition, with release 5.5, InnoDB is now the default storage engine for the MySQL Database, delivering ACID transactions, referential integrity and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

• Significantly improved performance on Windows, with various Windows specific features and improvements
• Higher availability, with new semi-synchronous replication and Replication Heart Beat
• Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new Performance Schema monitoring capability.

Functionality Added or Changed:

Important Change: The YEAR(2) data type is now deprecated because it is problematic. Support for YEAR(2) will be removed in a future release of MySQL. For more information, see YEAR(2) Limitations and Migrating to YEAR(4) (http://dev.mysql.com/doc/refman/5.5/en/migrating-to-year4.html).

Bugs Fixed:

• InnoDB: An assertion could be raised if an InnoDB table was moved to a different database using ALTER TABLE ... RENAME while the database was being dropped by DROP DATABASE. (Bug #13982017)
• Sessions could end up deadlocked when executing a combination of SELECT, DROP TABLE, KILL, and SHOW ENGINE INNODB STATUS. (Bug #60682, Bug #12636001)

Rilasciato VirtualBox 4.1.16, software freeware di virtualizzazione per sistemi Windows, Linux, Mac OS X. Download da questa pagina.

This is a maintenance release. The following items were fixed and/or added:

• VMM: fixed a Guru Meditation VERR_ACCESS_DENIED with certain guests (bugs #7589, #8247)
• VMM: fixed a Guru Meditation VERR_PAGE_TABLE_NOT_PRESENT with Ubuntu 32-bit guests with nested paging enabled on AMD CPUs (bug #10183)
• VMM: preserve segment limits and attributes when switching to unreal mode required for some legacy guests to work properly (VT-x without unrestricted guest execution only; bug #9941)
• VMM: fixed a VM hang after a resume from pause / savestate with SMP guests in rare cases
• 3D Support: several fixes for the Windows WDDM video driver crash
• NAT: fixed a crash on attempt to process ICMP datagram under some circumstances (bug #10527)
• Host-only Networking: lifted the maximal number of interfaces to 128 on Linux and Mac OS X hosts (there is no such limitation for Solaris and Windows hosts)
• EFI: fixed wrong SEC/PEI Core entry point calculation (bug #10531)
• VRDP: fixed a display update problem (bug #10503)
• Main: set the proper VM state if savestate failed for some reason (bug #6189)
• Main: more useful error message if a medium is inaccessible
• VBoxManage: fixed controlvm savestate if the VM is already paused
• Mac OS X hosts: addressed issues running on Mountain Lion Preview 3 (bug #10267)
• Linux hosts: Linux 3.4 compile fixes
• Linux hosts: fixed wrong help path in some rpm-based packages (bug #10418)
• Guest Additions: fixed handling of custom environment variables during VBoxManage guestcontrol execute(bug #10581)
• Windows Additions: fixed guest driver crash of VBoxSF in certain cases (4.1.10 regression, bug #10408)
• Windows Additions: don't load the WDDM driver if 3D support is not available for Windows 8 guests to keep the guest maintainable in that case (still better to miss some features than providing a blank screen)
• Solaris Additions: added support for X.org Server 1.11 and 1.12

Annunciato il rilascio di MySQL 5.5.21, nuova versione del RDMBS (Relational Database Management System) open source

MySQL 5.5.21 is a new version of the 5.5 production release of the world's most popular open source database. MySQL 5.5.21 is recommended for use on production systems. MySQL 5.5 includes several high-impact enhancements to improve the performance and scalability of the MySQL Database, taking advantage of the latest multi-CPU and multi-core hardware and operating systems. In addition, with release 5.5, InnoDB is now the default storage engine for the MySQL Database, delivering ACID transactions, referential integrity and crash recovery by default.

Functionality Added or Changed

A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows or Mac OS X to be used in the project name. (Bug #13551687)

Bugs Fixed

Performance: InnoDB Storage Engine: Memory allocation for InnoDB tables was reorganized to reduce the memory overhead for large numbers of tables or partitions, avoiding situations where the "resident set size" could grow regardless of FLUSH TABLES statements. The problem was most evident for tables with large row size. Some of the memory that was formerly allocated for every open table is now allocated only when the table is modified for the first time. (Bug #11764622, Bug #57480)

Incompatible Change: An earlier change (in MySQL 5.1.62 and 5.5.21) was found to modify date-handling behavior in General Availability-status series (MySQL 5.1 and 5.5). This change has been reverted.

The change was that several functions became more strict when passed a DATE() function value as their argument, thus they rejected incomplete dates with a day part of zero. These functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(), DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(), TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The previous behavior has been restored. (Bug #13458237)

InnoDB Storage Engine: A Valgrind error was fixed in the function os_aio_init(). (Bug #13612811)

InnoDB Storage Engine: The server could crash when creating an InnoDB temporary table under Linux, if the $TMPDIR setting points to a tmpfs filesystem and innodb_use_native_aio is enabled, as it is by default in MySQL 5.5.4 and higher. The entry in the error log looked like:

101123 2:10:59 InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
The crash occurred because asynchronous I/O is not supported on tmpfs in some Linux kernel versions. The workaround was to turn off the innodb_use_native_aio setting or use a different temporary directory. The fix causes InnoDB to turn off the innodb_use_native_aio setting automatically if it detects that the temporary file directory does not support asynchronous I/O. (Bug #13593888, Bug #11765450, Bug #58421)

InnoDB Storage Engine: References to C preprocessor symbols and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code. They were only used in debug builds instrumented for Valgrind. They are replaced by calls to the UNIV_MEM_INVALID() macro. (Bug #13418934)

InnoDB Storage Engine: The MySQL server could halt with an assertion error:

InnoDB: Failing assertion: page_get_n_recs(page) > 1
Subsequent restarts could fail with the same error. The error occurred during a purge operation involving the InnoDB change buffer. The workaround was to set the configuration option innodb_change_buffering=inserts. (Bug #13413535, Bug #61104)

InnoDB Storage Engine: With 1024 concurrent InnoDB transactions running concurrently and the innodb_file_per_table setting enabled, a CREATE TABLE operation for an InnoDB table could fail. The .ibd file from the failed CREATE TABLE was left behind, preventing the table from being created later, after the load had dropped.

The fix adds error handling to delete the erroneous .ibd file. This error was less likely to occur in MySQL 5.5 and 5.6, because raising the number of InnoDB undo slots increased the number of simultaneous transactions needed to trigger the bug, from 1K to 128K. (Bug #12400341)

Replication: Executing mysqlbinlog with the --start-position=N option, where N was equal either to 0 or to a value greater than the length of the dump file, caused it to crash.

This issue was introduced in MySQL 5.5.18 by the fix for Bug #32228 and Bug #11747416. (Bug #13593869, Bug #64035)

Replication: On Windows replication slave hosts, STOP SLAVE took an excessive length of time to complete when the master was down. (Bug #11752315, Bug #43460)

A query that used an index on a CHAR column referenced in a BETWEEN clause could return invalid results. (Bug #13463488, Bug #63437)

Expressions that compared a BIGINT column with any non-integer constant were performed using integers rather than decimal or float values, with the result that the constant could be truncated. This could lead to any such comparison that used <, >, <=, >=, =, !=/<>, IN, or BETWEEN yielding false positive or negative results. (Bug #13463415, Bug #11758543, Bug #63502, Bug #50756)

When the optimizer performed conversion of DECIMAL values while evaluating range conditions, it could produce incorrect results. (Bug #13453382)

When running mysqldump with both the --single-transaction and --flush-logs options, the flushing of the log performed an implicit COMMIT (see Section 12.3.3, "Statements That Cause an Implicit Commit"), causing more than one transaction to be used and thus breaking consistency. (Bug #12809202, Bug #61854)

It was possible in the event of successive failures for mysqld_safe to restart quickly enough to consume excessive amounts of CPU. Now, on systems that support the sleep and date system utilities, mysqld_safe checks to see whether it has restarted more than 5 times in the current second, and if so, waits 1 second before attempting another restart. (Bug #11761530, Bug #54035)

When used with the --xml option, mysqldump --routines failed to dump any stored routines, triggers, or events. (Bug #11760384, Bug #52792)

It was possible on replication slaves where FEDERATED tables were in use to get timeouts on long-running operations, such as Error 1160 Got an error writing communication packets. The FEDERATED tables did not need to be replicated for the issue to occur. (Bug #11758931, Bug #51196)

References: See also Bug #12896628, Bug #61790.

If an attempt to initiate a statement failed, the issue could not be reported to the client because it was not prepared to receive any error messages prior to the execution of any statement. Since the user could not execute any queries, they were simply disconnected without providing a clear error.

After the fix for this issue, the client is prepared for an error as soon as it attempts to initiate a statement, so that the error can be reported prior to disconnecting the user. (Bug #11755281, Bug #47032)

Using myisamchk with the sort recover method to repair a table having fixed-width row format could cause the row pointer size to be reduced, effectively resulting in a smaller maximum data file size. (Bug #48848, Bug #11756869)

On Windows, the server incorrectly constructed the full path name of the plugin binary for INSTALL PLUGIN and CREATE FUNCTION ... SONAME. (Bug #45549, Bug #11754014)

The stored routine cache was subject to a small memory leak that over time or with many routines being used could result in out-of-memory errors. (Bug #44585, Bug #11753187)

Il changelog completo è disponibile a questa pagina. Download a partire da questa pagina.

Annunciato il rilascio della versione 4.1. di VirtualBox

This is a maintenance release. The following items were fixed and/or added:

• VMM: fixed PAE guests running on 32-bit hosts (4.0 regression; bug #9458)
• VMM: fixed INVALID_PARAMETER guru meditation caused by insufficient memory conditions (4.1.0 regression; bug #9240)
• VMM: fixed clobbered CPU registers during stos/lods/ins/outs emulation under rare circumstances
• VMM: another fix for 64-bit guests on recent AMD CPUs
• USB: make device capturing work on Windows hosts with usbhub class filter drivers installed (bug #9298); bugfixes for Windows host USB support
• VMDK: fixed progress indicator when creating split VMDK images
• Floppy: fixed medium size detection for physical mediums (Windows hosts only)
• Main: fixed taking screen shots (e.g. the preview window) for headless VMs if the Guest Additions are active
• 3D Support: fixed incorrect rendering and possible crashes when switching to/from fullscreen with enabled 2D acceleration
• 3D Support: fixed compiz under ubuntu 9.10
• Guest control: Miscellaneous small bugfixes
• Linux / Solaris hosts: don't use hard links in packages (4.1.2 regression; bug #9441)
• Mac OS X hosts: fix installation issues when installed as root (bug #1578)
• Mac OS X hosts: fixed packet capture issues with vboxnetX host-only interfaces (bug #8076)
• Solaris hosts: fixed incoming multicast packets for Crossbow based bridged networking (bug #9532)
• Solaris hosts: fixed starting EFI guests due to missing EFI ROM files (bug #9535)
• Windows hosts installer: fixed ADDLOCAL usage on command line (4.1.0 regression; bug #9488)
• Windows hosts installer: fixed dangling shortcut to the .chm help file (bug #9646)
• Windows hosts installer: try to fix installation error 2869 which appeared under certain circumstances (bug #9664)
• Windows hosts: VBoxHeadless should never open a separate console window (bug #3549)
• Guest Additions: fixed hang while waiting for guest execution output (4.1.2 regression; bug #9446)
• Linux Additions: add support for X.Org Server 1.11 (bug #9519)
• Linux Additions: suppress an incorrect error message and allow a shared folder to be mounted in multiple places (bug #9627)
• Linux Additions: start VBoxService correctly on openSUSE 12.1 (bug #6229)
• Linux Additions: properly finish the installation even if the compilation of the DRM module fails (which is not fatal)
• Solaris Additions: fixed memory leaks and panics while mounting (from console) and unmounting shared folders.
• Windows Additions: fixed swapped mouse cursor hotspot coordinates (4.1.0 regression; bug #9447)
• Windows Additions: fixed PAGE_FAULT_IN_NONPAGED_AREA BSOD in VBoxDisp.dll when running SnippingTool (bug #9508)
• Windows Additions: make image viewer work correctly with Aero enabled (Vista and Windows 7)
• Windows Additions: fixed incorrect window border blurs under Aero with ATI cards (Vista and Windows 7)
• Windows Additions: fixed incorrect rendering when moving 3D applications outside guest desktop and back under Aero (Vista and Windows 7)
• Windows Additions: fixed guest hangs when switching back from fullscreen text mode apps (bug #9636)

Intel ha rilasciato il SDK 1.5 di OpenCL. Download del SDK per sistemi Windows e Linux a partire da questa pagina.

Performance Enhancements

• Intel® Advanced Vector Extensions (AVX) code generation – full utilization of the Intel® 2nd generation Core™ Processors SIMD vector width.
• Improved barriers – performance improvement when using the built-in work-group barrier function.

OpenCL Runtime Features

• New Intel extension: cl_intel_immediate_execution – Immediate Command Execution is an extension which enables you to execute OpenCL commands in a single-threaded manner, using the calling thread to perform the actual execution.

OpenCL Development Tools

• Intel® OpenCL SDK Debugger (beta version) – The Intel® OpenCL SDK Debugger is a Microsoft* Visual Studio* 2008 plug-in, which enables you to set breakpoints inside OpenCL kernels, examine values of variables, memory and stack trace.
• Intel® Graphics Performance Analyzers 4.2 (Intel® GPA) support of Intel® OpenCL SDK 1.5 provides full coverage of OpenCL on CPU profiling, including:
  distribution of the OpenCL commands and kernels, flow and dependencies between commands, duration of commands and kernels execution.
• New features in the Intel® OpenCL SDK Offline Compiler: Linux* OS support