The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

MySQL 5.5 is now supported as of version 11.31.1.2

Discussion in 'Database Discussions' started by ASTRAPI, Oct 8, 2011.

  1. ASTRAPI

    ASTRAPI Well-Known Member

    Joined:
    Jul 8, 2008
    Messages:
    321
    Likes Received:
    0
    Trophy Points:
    16
    Hello

    I want to ask please as i am using on my database only innodb if the upgrade to MySQL 5.5 on 11.31.1.2 will be smooth or if i have to do something after or before the upgrade to work?

    I am asking as i was read that the cpanel upgrade to new mysql will auto add a line to my.cnf to avoid by default the use of Innodb and if it is true it will make my site offline until i remove that line?

    Also can you please name a few changes on new Mysql 5.5 about performance?

    Thank you
     
  2. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,458
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Please be advised that the 11.31 release is a development release. It is not recommended for production use.[/p] You should be very comfortable with diving into Perl code, patching and other highly technical skills before upgrading to cPanel & WHM 11.31. Further information about this release is available here: 11.32 Development Version Announcement - cPanel Inc.


    We add the following the /etc/my.cnf upon upgrading to MYSQl 5.5:

    Code:
    innodb_file_per_table =1
    default-storage-engine = MyISAM
    
    Neither of these should cause a problem with existing databases, regardless of their storage engine.

    What can be a problem is the configuration directives that MySQL dropped or renamed in version 5.5. These tend to cause fatal startup errors.

    The following configuration items were dropped:

    default-table-type
    log-long-format
    log-update
    master-host
    master-user
    master-password
    master-port
    master-connect-retry
    master-ssl
    master-ssl-ca
    master-ssl-capath
    master-ssl-cert
    master-ssl-cipher
    master-ssl-key
    safe-show-database
    sql-bin-update-same
    set-variable
    skip-safemalloc

    The following were renamed:

    default-character-set -> character-set-server
    default-collation -> collation-server
    delay-key-write-for-all-tables -> delay-key-write=ALL
    enable-locking -> external-locking
    skip-locking -> skip-external-locking
    log-bin-trust-routine-creators -> log-bin-trust-function-creators
    skip-symlink -> skip-symbolic-links
    use-symbolic-links -> symbolic-links
    warnings -> log-warnings

    [mysql]
    no-named-commands -> skip-named-commands
    no-pager -> skip-pager
    no-tee -> skip-tee

    [mysqlbinlog]
    position -> start-position

    [mysqldump]
    all -> create-options
    first-slave -> lock-all-tables

    [mysqld_multi]
    config-file -> defaults-extra-file

    You should make the appropriate changes to /etc/my.cnf before upgrading.
     
  3. ASTRAPI

    ASTRAPI Well-Known Member

    Joined:
    Jul 8, 2008
    Messages:
    321
    Likes Received:
    0
    Trophy Points:
    16
    What is this for?


    How is possible to not create a problem as you set as default mysql engine the Myisam as i use Innodb?

    Thank you
     
Loading...

Share This Page