MySQL Community Server 5.5.25a has been released
Dear MySQL users, MySQL 5.5.25a is a new version of the 5.5 production release of the world's most popular open source database. MySQL 5.5.25a is recommended for use on production systems. MySQL 5.5.25a is a replacement of MySQL 5.5.25, in that version a regression bug was detected in the optimizer (Bug #65745). Because of this, MySQL 5.5.25 has been removed from the download sites. We recommend that users who have installed MySQL 5.5.25 upgrade to MySQL 5.5.25a at the earliest opportunity. That bug is specific to MySQL 5.5.25, other versions are not affected. 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. For a more complete look at what's new in MySQL 5.5, please see the following resources: MySQL 5.5 is GA, Interview with Tomas Ulin: http://dev.mysql.com/tech-resources/interviews/thomas-ulin-mysql-55.html Documentation: http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html Whitepaper: What's New in MySQL 5.5: http://dev.mysql.com/why-mysql/white-papers/mysql-wp-whatsnew-mysql-55.php If you are running a MySQL production level system, we would like to direct your attention to MySQL Enterprise Edition, which includes the most comprehensive set of MySQL production, backup, monitoring, modeling, development, and administration tools so businesses can achieve the highest levels of MySQL performance, security and uptime. http://mysql.com/products/enterprise/ For information on installing MySQL 5.5.25a on new servers, please see the MySQL installation documentation at http://dev.mysql.com/doc/refman/5.5/en/installing.html For upgrading from previous MySQL releases, please see the important upgrade considerations at: http://dev.mysql.com/doc/refman/5.5/en/upgrading.html MySQL Database 5.5.25a is available in source and binary form for a number of platforms from our download pages at: http://dev.mysql.com/downloads/mysql/ 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 The following sections list the changes in the MySQL source code since the previous released versions, MySQL 5.5.25 (withdrawn) and MySQL 5.5.24. They may also be viewed online at: http://dev.mysql.com/doc/refman/5.5/en/news-5-5-25a.html http://dev.mysql.com/doc/refman/5.5/en/news-5-5-25.html Enjoy! D.1.2. Changes in MySQL 5.5.25a (2012-July-05) Note Due to MSI restrictions, the MSI packages of MySQL 5.5.25a will treat the version as 5.5.26 internally; for example, as displayed by the Installation Wizard. MySQL itself reports the version as 5.5.25a; for example, if you check the value of the VERSION() SQL function or the version system variable. Bugs Fixed * A regression bug in the optimizer could cause excessive disk usage for UPDATE statements. (Bug #65745, Bug #14248833) D.1.3. Changes in MySQL 5.5.25 (2012-May-30) Note MySQL 5.5.25 is superseded by MySQL 5.5.25a due to a regression bug that can cause excessive disk usage (for details, see Bug #65745). Current users of 5.5.25: Monitor disk usage and upgrade to 5.5.25a as soon as that is made available. Users contemplating upgrades to 5.5.25: Defer and upgrade to 5.5.25a instead when that is made available. Functionality Added or Changed * Important Change: Replication: The SHOW BINARY LOGS statement (and its equivalent SHOW MASTER LOGS) may now be executed by a user with the REPLICATION CLIENT privilege. (Formerly, the SUPER privilege was necessary to use either form of this statement.) * The --safe-mode server option now is deprecated and will be removed in MySQL 5.6. Bugs Fixed * Performance: InnoDB: Improved the algorithm related to adaptive flushing. This fix increases the rate of flushing in cases where compression is used and the data set is larger than the buffer pool, leading to eviction. (Bug #13990648, Bug #65061) * InnoDB: In a transaction using the REPEATABLE READ isolation level, an UPDATE or DELETE
Installation of MySQL in Redhat Linux 6.0
Hi all, I am using Redhat Linux 6.0 (64 bit) machine, in this machine I am trying to install MySQL5.5 glibc23 server and client packages as a root user. While installing I am getting the following error: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) When I try to install the MySQL rhel6 package then MySQL is installed and service also started successfully. But I am not able to install the glibc23 package with SELinux is enabled in my Redhat linux machine. After Disabling the SELinux, I was able to install MySQL glibc23 package. I want to know why MySQL glibc23 package is not able to install with SELinux enabled?? Thanks in advance. Regards, Manivannan S DISCLAIMER: This email message and all attachments are confidential and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or to mailad...@spanservices.com and destroy the original message. Opinions, conclusions and other information in this message that do not relate to the official business of SPAN, shall be understood to be neither given nor endorsed by SPAN.
Re: Installation of MySQL in Redhat Linux 6.0
Am 05.07.2012 16:30, schrieb Manivannan S.: Hi all, I am using Redhat Linux 6.0 (64 bit) machine, in this machine I am trying to install MySQL5.5 glibc23 server and client packages as a root user. While installing I am getting the following error: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) When I try to install the MySQL rhel6 package then MySQL is installed and service also started successfully. But I am not able to install the glibc23 package with SELinux is enabled in my Redhat linux machine. After Disabling the SELinux, I was able to install MySQL glibc23 package. I want to know why MySQL glibc23 package is not able to install with SELinux enabled?? Thanks in advance. wrong mailing-list this is a RHEL/CentOS problem setroubleshoot-doc.x86_64 : Setroubleshoot documentation setroubleshoot-plugins.noarch : Analysis plugins for use with setroubleshoot setroubleshoot.x86_64 : Helps troubleshoot SELinux problems setroubleshoot-server.x86_64 : SELinux troubleshoot server signature.asc Description: OpenPGP digital signature
group_key?
Here is something queer: select ifnull(email, round(1 * rand(), 1)) as ux, count(*) from nam group by ux; ERROR 1062 (23000): Duplicate entry '2514.0' for key 'group_key' I have a name-list, with e-mail address or not. I wanted to fill the NULL e-mail addresses with something random, and, I hope, unique. (ROUND is there only to make that surprising error liklier.) The field email is not UNIQUE, not a key, no intention of making it such. Why this error? Is RAND called more than once for each record? I tryed also UUID, but that came with its own shortcoming: if the UUID call were the whole field, it indeed was once called for every record, but if argument to IFNULL, only once for the whole query. Version 5.5.8 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: group_key?
Hi, you might have hit: http://bugs.mysql.com/bug.php?id=58081 Cheers Claudio 2012/7/5 Halász Sándor h...@tbbs.net Here is something queer: select ifnull(email, round(1 * rand(), 1)) as ux, count(*) from nam group by ux; ERROR 1062 (23000): Duplicate entry '2514.0' for key 'group_key' I have a name-list, with e-mail address or not. I wanted to fill the NULL e-mail addresses with something random, and, I hope, unique. (ROUND is there only to make that surprising error liklier.) The field email is not UNIQUE, not a key, no intention of making it such. Why this error? Is RAND called more than once for each record? I tryed also UUID, but that came with its own shortcoming: if the UUID call were the whole field, it indeed was once called for every record, but if argument to IFNULL, only once for the whole query. Version 5.5.8 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- Claudio
Re: GA download reverted back to 5.5.24?
For those interested 5.5.25a has been released overnight, long after oracle claimed it was there. frankly., I think they ought to have use 5.5.26. To those who replied to me directly, a few facts... 1/ it never affected me directly - my gripe with them was on principle and their actions (or lack thereof) towards those that were affected 2/ to the wanker who said people deserve what they get for untesting on DEV bed first ... this is true _IF_ it was a major release. (as I hope we all do) _BUT_ you don't expect to get fucked over by a point release, to have that happen, shows incompetenceon the part of the software developer, not the users. On Sat, 2012-06-30 at 14:15 +1000, Noel Butler wrote: I wonder if you would have the same opinion to say your Operating System environment, Apache, php, any mainstream server daemon, how about they pull the current version for a serious bug, but dont tell anyone... Oracle have been quick to announce new releases of mysql, but failed to issue a notice saying uhoh, you better not use it instead, putting a small notice, where, on a fricken manual page FFS. who the hell reads that! and they say use version a which does not even exist, I'd hate to think of how many high profile sites are at risk of being screwed over by yet MORE oracle incompetence. No one would think any less of them if they sent that notice, many would be appreciative, but to hide such a serious issue that was enough for them to withdraw and remove that version, is outright despicable. On Fri, 2012-06-29 at 22:58 -0400, Govinda wrote: That was nice of oracle to announce this wasn't it ...(/sarcasm) I am not aligned with any side.. and I am also not known/qualified/respected in this group enough to make much of a statement... but: IMHO, In almost all matters, *appreciation* is the only approach that will serve... let alone sustain happiness... ...and especially when we consider what little we must give to have right to use MySQL. Sure, desire for better communication/usability makes total sense.. but I am just also observing/suggesting: please add (positively) to the atmosphere.. for everyones' sake. Just us humans under the hood. -Govinda signature.asc Description: This is a digitally signed message part
Re: group_key?
2012/07/05 21:01 +0200, Claudio Nanni you might have hit: http://bugs.mysql.com/bug.php?id=58081 Indeed -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
