Hide Forgot
Description of problem: MySQL InnoDB Plugin was disabled at MySQL 5.1.42-4. | * Fri Jan 8 2010 Tom Lane <tgl> 5.1.42-4 | - Disable building the innodb plugin; it tickles assorted gcc bugs and | doesn't seem entirely ready for prime time anyway. But InnoDB Plugin became GA at MySQL 5.1.46, and in MySQL 5.1.52 (RHEL6 uses) it has been upgraded to 1.0.13. http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html So I think now InnoDB Plugin has production quality. InnoDB Plugin has many usable features and good performance, so I want to use it in RHEL 6.2 or later. Thanks, Version-Release number of selected component (if applicable): 5.1.52
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The InnoDB plugin) is supported only on the x86 and x86_64 architectures.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,2 +1 @@ -The InnoDB plugin) is supported only on +Red Hat Enterprise Linux 6.3 provides the MySQL InnoDB storage engine as a plug-in for AMD64 and Intel 64 architectures. The plugin offers additional features and better performance than the built-in InnoDB storage engine.-the x86 and x86_64 architectures.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0874.html