Skip navigation links
1.5 MySQL Information Sources »
Section Navigation      [Toggle]

1.4.2. What Is Planned for MySQL 5.4

Note

This section remains subject to change as long as MySQL 5.4 development is in its early stages.

The following features are expected to be added to, or change in MySQL 5.4:

  • Several small, high-impact changes to enhance scalability and performance in MySQL Server: Scalability improvements on multi-core CPUs, InnoDB I/O subsystem changes, enhanced Solaris support, diagnostic and monitoring capability improvements, and better “out of box” configuration choices for MySQL operation on servers with multiple cores are large amounts of memory.

  • Improvements in the INFORMATION_SCHEMA database, with the addition of the INFORMATION_SCHEMA.PARAMETERS table, and new columns added to INFORMATION_SCHEMA.ROUTINES (see The INFORMATION_SCHEMA PARAMETERS Table, and Section 19.14, “The INFORMATION_SCHEMA ROUTINES Table”).

  • Optimizer enhancements for faster subqueries and joins, including batched index access of table rows for sequences of disjoint ranges by the MyISAM and InnoDB storage engines.

  • The syntax for the LOCK TABLES statement is extended to support transactional table locks that do not commit transactions automatically. Following LOCK TABLES ... IN SHARE MODE or LOCK TABLES ... IN EXCLUSIVE MODE, you can access tables not mentioned in the LOCK TABLES statement. You can now also issue these extended LOCK TABLES statements many times in succession, adding additional tables to the locked set, and without unlocking any tables that were locked previously. When using LOCK TABLES with IN SHARE MODE or IN EXCLUSIVE MODE, tables are not unlocked until the transaction ends.

    The behavior of LOCK TABLES when not using IN SHARE MODE or IN EXCLUSIVE MODE remains unchanged.

  • Enhancements to XML functionality, including a new LOAD XML statement (see LOAD XML Syntax).

  • Supports for an interface for semisynchronous replication: A commit performed on the master side blocks before returning to the session that performed the transaction until at least one slave acknowleges that it has received and logged the events for the transaction. Semisynchronous replication is implemented through an optional plugin component. See Semisynchronous Replication

  • Support for the SQL standard SIGNAL and RESIGNAL statements. See SIGNAL and RESIGNAL.

  • Support for extended comments for tables, columns, and indexes.

The following constructs are deprecated and have been removed for MySQL 5.4. Where alternatives are shown, applications should be updated to use them.

  • The table_type system variable (use storage_engine).

    The TYPE table option to specify the storage engine for CREATE TABLE or ALTER TABLE (use ENGINE).

    The SHOW TABLE TYPES SQL statement (use SHOW ENGINES).

  • The log_bin_trust_routine_creators variable (use log_bin_trust_function_creators).

  • TIMESTAMP(N): The ability to specify a display width of N (use without N).

  • The SHOW INNODB STATUS and SHOW MUTEX STATUS SQL statements (use SHOW ENGINE INNODB STATUS for both of these).

  • The LOAD TABLE ... FROM MASTER and LOAD DATA FROM MASTER SQL statements.

  • The SHOW PLUGIN SQL statement (use SHOW PLUGINS).

  • The --master-xxx server options to set replication parameters (use the CHANGE MASTER TO statement instead): --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.