Bug 437098
Summary: | poor performance with multiple queries | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Adam Stokes <astokes> |
Component: | mysql | Assignee: | Tom Lane <tgl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.1 | CC: | byte, denis, hhorak, k.georgiou, riaanvn |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 5.0.45-7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-26 00:52:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Adam Stokes
2008-03-12 13:24:15 UTC
This also applies to RHEL5.1 (stable) with all updates. Why is this bug given a "low" severity? It currently makes any Red Hat shipped version of MySQL practically unusable for any scenario where InnoDB is used. This bug forces us to use mysql.com provided community-releases as it is. I was hoping it would be resolved in RHEL5.2, but if this still applies to the package currently included in 5.3 my hopes are not up. Some priority would be welcome. Regards Denis Denis, Thanks for the update -- Ive raised the severity/priority flags. May I also suggest that if you have a support contract with Red Hat that you file a support request referencing this BZ as well? Thank you, Adam Adam, I have already done this, is it enough to include a link to this BZ bugid in the description? Regards Denis Hi Denis, That should be enough -- our engineers will triage that support request up to the appropriate backline engineers to be handled. Thank you for your support. Adam If you're seeing this in 5.0.45 then that upstream fix was already applied, and you're going to need to talk to MySQL AB about the problem --- fixing such things is far beyond my knowledge of that code. I am sorry about the misunderstanding here. I do not see this behaviour with 5.0.45, but with 5.0.22 which is what RHEL5.1 ships. If this means I should create a separate bug instead, then I will proceed to do so. Again sorry. Denis 5.0.45 is scheduled to go out in RHEL 5.2, so you just need to wait a bit ... Can someone with the necessary permissions please change the Version field from 5.3 to 5.1. That way it will not mislead any more people (like what happened in Comment #1). Fixed in RHEL 5.2 update. |