have_innodb removed in mysql 5.6

Bug #1194988 reported by Andrew Garner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
holland-backup
Fix Committed
High
Andrew Garner

Bug Description

This is used by mysqldump-lvm to determine whether we should set any innodb parameters.

This is documented in the MySQL docs here:

"* have_innodb

YES if mysqld supports InnoDB tables. DISABLED if --skip-innodb is used.

This variable was removed in MySQL 5.6.1. Use SHOW ENGINES instead."

This sort of breaks mysqldump-lvm with MySQL 5.6, since we'll fail to set a proper innodb-log-file-size. 5.6 will automatically regenerate new logs - but this might generate a lot of unnecessary io on the snapshot and eat up snapshot space.

Holland needs to check SHOW ENGINES instead.

Andrew Garner (muzazzi)
Changed in holland-backup:
milestone: none → 1.0.12
Revision history for this message
Andrew Garner (muzazzi) wrote :
Changed in holland-backup:
importance: Undecided → High
status: New → Fix Committed
status: Fix Committed → In Progress
assignee: nobody → Andrew Garner (muzazzi)
Andrew Garner (muzazzi)
Changed in holland-backup:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.