Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionChristopher Hirschmann
2012-02-02 00:00:48 UTC
Description of problem:
mysql-server Package in RHEL 6 is affected by this MySQL bug:
http://bugs.mysql.com/bug.php?id=56423
Version-Release number of selected component (if applicable):
5.1.52
How reproducible:
always, see test case attached to MySQL bugreport
Steps to Reproduce:
1. create a table with the appropiate content (see test case attached to MySQL bugreport)
2. run a 'select *' on that table to see what it contains
3. now run a 'create … select' (as shown in the test case attached to MySQL bugreport) and look at the results of the 'create' part of that statement
Actual results:
'create … select' statement produces fewer results than corresponding 'select' statement
Expected results:
'create … select' and 'select' statements should produce exactly the same results
Additional info:
Fixed in MySQL 5.1.53 and newer, but this bug seems have had many regressions, so it might be a good idea to implement some kind of regression test for this, too.
This is a serious MySQL bug, that makes affected MySQL versions unfit for production use. The bugfix should definetly be backported to the mysql-server package in RHEL 6.
Our client wasn't even aware that his application used these kind of statements, because they had been created by a framework.
The upstream fix for this should be included in our recent security update:
RHSA-2012:0105 https://rhn.redhat.com/errata/RHSA-2012-0105.html
although this bug is not listed there since it is not a security issue.