Buy Percona SupportEmergency? Get 24/7 Help Now!

Enforcing Storage Engine

Percona Server has implemented variable which can be used for enforcing the use of a specific storage engine.

When this variable is specified and a user tries to create a table using an explicit storage engine that is not the specified enforced engine, he will get either an error if the NO_ENGINE_SUBSTITUTION SQL mode is enabled or a warning if NO_ENGINE_SUBSTITUTION is disabled and the table will be created anyway using the enforced engine (this is consistent with the default MySQL way of creating the default storage engine if other engines aren’t available unless NO_ENGINE_SUBSTITUTION is set).

In case user tries to enable enforce_storage_engine with engine that isn’t available, system will not start.

Note

If you’re using enforce_storage_engine, you must either disable it before doing mysql_upgrade or perform mysql_upgrade with server started with --skip-grants-tables.

Version Specific Information

System Variables

variable enforce_storage_engine
Command Line:Yes
Config File:Yes
Scope:Global
Dynamic:No
Variable Type:String
Default Value:NULL

Note

This variable is not case sensitive.

Example

Adding following option to my.cnf will start the server with InnoDB as enforced storage engine.

enforce_storage_engine=InnoDB
Download PDF Manual

Table Of Contents

This Page

Percona Server Series

This documentation is developed in Launchpad as part of the Percona Server 5.6.
If you spotted inaccuracies, errors, don't understood it or you think something is missing or should be improved, please file a bug.

General Inquiries

For general inquiries, please send us your question and someone will contact you.


Ask Me!