Bug #26391 some optional storage engines cannot be disabled with common --skip syntax

• Submitted: 15 Feb 2007 4:59
• Modified: 16 Mar 2007 15:22
• Reporter: Sean Pringle
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S4 (Feature request)
• Version: 5.0, 5.1
• Assigned to: MC Brown
• CPU Architecture: Any
• Tags: bfsm_2007_03_01

[15 Feb 2007 4:59] Sean Pringle

Description:
The FEDERATED storage engine cannot be disabled on the fly in a syntactically similar way to other optional storage engines. 

These exist:

--skip-innodb, --skip-bdb, --skip-merge

This does not exist:

--skip-federated

Also, given the above, 13.5.4.13. SHOW ENGINES Syntax section in the manual is unclear when it implies that any engine make be disabled with --skip-(engine):

"You might also see DISABLED for a storage engine if the server was compiled to support it, but was started with a --skip-engine  option. For example, --skip-innodb disables the InnoDB engine."

http://dev.mysql.com/doc/refman/5.0/en/show-engines.html
http://dev.mysql.com/doc/refman/5.1/en/show-engines.html

How to repeat:
Start mysqld with --skip-federated

070215 14:47:46  mysqld started
070215 14:47:46 [ERROR] /home/sean/mysql/src/5115/libexec/mysqld: unknown option '--skip-federated'

Suggested fix:
Allow all optional storage engines to be disabled using common syntax: --skip-(engine).

[16 Feb 2007 12:49] Valeriy Kravchuk

Thank you for a reasonable feature request.

[16 Mar 2007 15:22] MC Brown

I've updated the manual to show that only the merge, InnoDB and BDB (5.0 only) can be disabled this way.