Changes in MySQL 8.0 •The  BACKUP_ADMIN  privilege is automatically granted to users with the  RELOAD  privilege when performing an in-place upgrade to MySQL 8.0.3 or higher. •From MySQL 8.0.13, because of differences between row-based or mixed replication mode and statement-based replication mode in the way that temporary tables are handled, there are new restrictions on switching the binary logging format at runtime. • SET @@SESSION.binlog_format  cannot be used if the session has any open temporary tables. • SET @@global.binlog_format  and  SET @@persist.binlog_format  cannot be used if any replication channel has any open temporary tables.  SET @@persist_only.binlog_format is allowed if replication channels have open temporary tables, because unlike  PERSIST , PERSIST_ONLY  does not modify the runtime global system variable value. • SET @@global.binlog_format  and  SET @@persist.binlog_format  cannot be used if any replication channel applier is running. This is because the change only takes effect on a replication channel when its applier is restarted, at which time the replication channel might have open temporary tables. This behavior is more restrictive than before.  SET @@persist_only.binlog_format  is allowed if any replication channel applier is running. InnoDB Changes • INFORMATION_SCHEMA  views based on  InnoDB  system tables were replaced by internal system views on data dictionary tables. Affected  InnoDB INFORMATION_SCHEMA  views were renamed: Table 2.16 Renamed InnoDB Information Schema Views Old Name New Name INNODB_SYS_COLUMNS INNODB_COLUMNS INNODB_SYS_DATAFILES INNODB_DATAFILES INNODB_SYS_FIELDS INNODB_FIELDS INNODB_SYS_FOREIGN INNODB_FOREIGN INNODB_SYS_FOREIGN_COLS INNODB_FOREIGN_COLS INNODB_SYS_INDEXES INNODB_INDEXES INNODB_SYS_TABLES INNODB_TABLES INNODB_SYS_TABLESPACES INNODB_TABLESPACES INNODB_SYS_TABLESTATS INNODB_TABLESTATS INNODB_SYS_VIRTUAL INNODB_VIRTUAL After upgrading to MySQL 8.0.3 or higher, update any scripts that reference previous  InnoDB INFORMATION_SCHEMA  view names. •The zlib library version bundled with MySQL was raised from version 1.2.3 to version 1.2.11. The zlib  compressBound()  function in zlib 1.2.11 returns a slightly higher estimate of the buffer size required to compress a given length of bytes than it did in zlib version 1.2.3. The  compressBound() function is called by  InnoDB  functions that determine the maximum row size permitted when creating compressed  InnoDB  tables or inserting and updating rows in compressed  InnoDB  tables. As a result, CREATE TABLE ... ROW_FORMAT=COMPRESSED ,  INSERT , and  UPDATE  operations with row sizes very close to the maximum row size that were successful in earlier releases could now fail. To avoid this issue, test  CREATE TABLE  statements for compressed  InnoDB  tables with large rows on a MySQL 8.0 test instance prior to upgrading. 274