Bug 806365 - mysql-server-5.0.95-1.el5_7.1 has Profiling disabled by default
Summary: mysql-server-5.0.95-1.el5_7.1 has Profiling disabled by default
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mysql
Version: 5.8
Hardware: All
OS: All
Target Milestone: rc
: ---
Assignee: Tom Lane
QA Contact: qe-baseos-daemons
Depends On:
TreeView+ depends on / blocked
Reported: 2012-03-23 15:00 UTC by Johnny Hughes
Modified: 2013-07-03 03:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-01-08 04:54:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0121 0 normal SHIPPED_LIVE Low: mysql security and bug fix update 2013-01-08 09:10:21 UTC

Description Johnny Hughes 2012-03-23 15:00:50 UTC
The default for the --enable-profiling option is off for mysql-5.0.95-1.el5_7.1 ... this is the opposite behavior from mysql-5.0.77-4.el5_6.6 (the previous version).

I have confirmed this issue on the CentOS, Oracle, and RHEL versions of mysql-server-5.0.95-1.el5_7.1

Please see this CentOS Bug for details:


Comment 1 Tom Lane 2012-03-24 01:10:12 UTC
Hm, it appears that somewhere between 5.0.77 and 5.0.95, upstream modified their configure script so that --enable-profiling defaults to off, where it used to default to on.  They did not bother to document this in the release notes AFAICS :-(.  I wonder why they did that...

Comment 3 RHEL Program Management 2012-05-08 17:17:47 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 8 errata-xmlrpc 2013-01-08 04:54:48 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.