MySQL 5.5

[el canadiano]

Hey guys,

I was wondering when MySQL 5.5 will be rolling out. I've been hearing about major improvements with InnoDB which results in a considerable speed increase.

Thanks,

el canadiano.

[Tony]

At this time cPanel does not support MySQL 5.5 so we're stuck with 5.1 for the time being. It's planned for 11.32 which if I was going to guess will arrive late this year.

[President-Anonymous]

At this time cPanel does not support MySQL 5.5 so we're stuck with 5.1 for the time being. It's planned for 11.32 which if I was going to guess will arrive late this year.

Cpanel currently does support MySQL 5.5

So when can we expect an update on this?

(I'm on a reseller account by the way)

[Tony]

Cpanel currently does support MySQL 5.5

So when can we expect an update on this?

(I'm on a reseller account by the way)

cPanel 11.32 still has not reached stable builds yet. If one is daring they can try it on their builds that are not quite production ready. Even when it reaches cPanel stable builds we're still a ways away from offering it. The reason being all our PHP builds will not work meaning everything needs to be recompiled. That means testing that to make sure it all works. Then we need to worry about backwards compatibility with applications as not all may support 5.5. Then finally we're rolling out builds of MySQL already which allow us to track usage and also using this information limit accounts. This would need to be available to do in MySQL 5.5 before we could use it as we would not want to lose such a valuable resource in having optimal server performance.

[President-Anonymous]

cPanel 11.32 still has not reached stable builds yet. If one is daring they can try it on their builds that are not quite production ready. Even when it reaches cPanel stable builds we're still a ways away from offering it. The reason being all our PHP builds will not work meaning everything needs to be recompiled. That means testing that to make sure it all works. Then we need to worry about backwards compatibility with applications as not all may support 5.5. Then finally we're rolling out builds of MySQL already which allow us to track usage and also using this information limit accounts. This would need to be available to do in MySQL 5.5 before we could use it as we would not want to lose such a valuable resource in having optimal server performance.

I find your slow release schedule, which keeps you on code as old or older than 2 years or more .... taxing.

just an opinion

[Cody R.]

I find your slow release schedule, which keeps you on code as old or older than 2 years or more .... taxing.

just an opinion

In an environment like ours we strive for stability / consistency so we try to run the most stable releases which are generally a few versions behind (or in the case of RHEL a few versions behind with important security fixes backported). If you require a more up-to-date environment we recommend a more customizable environment such as a dedicated server or VPS / a provider who supports the versions you need.

I do understand your frustration here however - we've just found that in an environment with so many users per machine a major upgrade to something like PHP or MySQL will tend to break things so we've opted for a slower more graceful upgrade cycle.

[President-Anonymous]

FYI: Your current version has a few known security vulnerabilities that we well documented.

I suggest you look into this.

[Cody R.]

FYI: Your current version has a few known security vulnerabilities that we well documented.

I suggest you look into this.

The version has been backported with the patches. If you believe otherwise please contact our support department .

[President-Anonymous]

The version has been backported with the patches. If you believe otherwise please contact our support department .

Not everything can be patched from backport. Some issues did indeed need to re-write of the newer build.

You risk your security and your customers (including mine) depending on a "patch and pray"

[Cody R.]

Not everything can be patched from backport. Some issues did indeed need to re-write of the newer build.

You risk your security and your customers (including mine) depending on a "patch and pray"

Unfortunately I don't think you fully understand how RHEL releases / backporting works. I'd recommend doing some research prior to jumping to such grandiose conclusions .

[President-Anonymous]

Unfortunately I don't think you fully understand how RHEL releases / backporting works. I'd recommend doing some research prior to jumping to such grandiose conclusions .

Please respectfully follow your own advise, before attempting to criticize mine. Thank you.

[Cody R.]

Please respectfully follow your own advise, before attempting to criticize mine. Thank you.

Absolutely! Please refer to RHEL site here: https://access.redha...es/backporting/. Please don't hesitate to contact our Support department if you want more information .

Cheers!

[President-Anonymous]

Absolutely! Please refer to RHEL site here: https://access.redha...es/backporting/. Please don't hesitate to contact our Support department if you want more information .

Cheers!

Nice public relations press release. Not nearly accurate, but nice.

Again, some things can not be patched 100% of the time. Sometimes an upgrade is required.

For most products our default policy is to backport security fixes, but we do sometimes provide version updates for some packages after careful testing and analysis. These are likely to be packages that have no interaction with others, or those used by an end-user, such as web browsers and instant messaging clients.

https://access.redhat.com/security/updates/backporting/

I would "suggest" you upgrade to MySQL 5.5 for better performance, security, and improved features.

We will re-visit this concept with you at a later time.